Visual Task Board in a Timeline Visualization

[tim_alman]

Has anyone attempted to use a visual task board in a timeline visualization?

I feel like I'm pretty close, but this is what I have so far...

I updated the VTB view to expose Due Date and a new choice field Type on the vtb_task table.   This allows you to access these fields when creating a new card on a visual task board.

I've also created a database view to join vtb_board to vtb_lane to vtb_card to vtb_task.   The 'Try It' link in the database view shows that the query is pulling the appropriate information.   See attachment for database view.

When I go to use the database view in the timeline visualization, I receive an error that says the Panel Color Key should be of type choice list.   I've also tried adding the approval and priority fields from vtb_task to the database view, but there was no change in the error.   It's as if the database view does not show the fields as choice fields.   See attachment for error.

I am open to any suggestions on the direction I'm heading or on other possible solutions/directions.

[ITSMgal]

What is the use case for doing this?

VTB is simply a way to visualize data that already exists. Why wouldn't you just go to the original data that you are also visualizing through VTB and use that as the source of the timeline visualization?

[tim_alman]

The Freeform VTB does not contain data that already exists; it's a task board of private tasks generated on the fly, instead of a Guided or Flexible VTB that is built off of incident, problem, change, etc.  

In this case, I am attempting to use the freeform VTB as a product roadmap.

[tim_alman]

I tracked down the getChoiceFieldNames in the ajax that fills in the possible choice fields from the table to the Panel Color Key field.   I pulled this code snippet and tried running this in a background script:

var roadmapUtil = new RoadmapUtil();

var choices = roadmapUtil.getChoiceFieldNames('u_vtb_visualization');

gs.log(choices.toString());

The result was an empty array.   For some reason, the ajax script is not returning the choice fields on the view.   You can verify it works by changing 'u_vtb_visualization' to 'incident'.

Has anyone seen similar issues with a database view?

[dshipley]

Any further progress on this?  I've encountered the same problem . . . using a different database view.  As far as the use case question . . . a database view exposes fields for filter conditions that are not available in either of the source tables - even through related fields.