Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Activity One: Add the Program and Program Projects to the EazyBI Data


  1. Navigate to the source data tab in eazybi and select "edit" next to the Jira Cube Import
  2. Ensure Category is selected at the top of the project dialogue. Select the Project Category for the program you are adding.
  3. Select the import button at the bottom of the page.

  Figure 1

Activity 2: Ensure the correct project teams are associated with the category


1) Validate that only the active teams in the program are associated with the project category.

  • Identify the active teams with the program RTE or other program leader.
  • Confirm the right teams are included in the EazyBI data:
    • Navigate to the program dashboard
    • Open the project select dropdown, and click the "+" symbol next to the new program name.
    • Validate the team projects match the list of the active teams confirmed by the RTE or other program leader
  • If only and all of the active teams appear, move on to the next activity. Otherwise, continue with the steps in this activity
  • If there are extra or missing teams, you must submit an Atlassian request to have the correct team projects associated to the project category.
    • Submit an request to the Jira support team in the #help-Atlassian slack channel
    • Include thest that the active team projects are associated with the category, and that all other teams are removed.
  • Once the request is complete, confirm in Eazybi with the method described above.


Activity: Update the  Project Switch Measure

  1. The project switch measure will update all dashboard reports using PI start dates or boundaries on the dashboard when a program is selected at the top of the dashboard:
  2. In the edit mode for any report, open the measures panel, and edit the user-defined measure entitled "Motherfuncktion"
  3. Insert the following code to the measure where indicated in figure 2:
    WHEN

  Generate(
    DescendantsSet([Project].CurrentHierarchyMember, [Project].CurrentHierarchy.Levels("Category")),
    [Project].CurrentHierarchyMember.Name,
    ","
  ) MATCHES ".*(^|,)NEW PROJECT CATEGORY NAME($|,).*"
  AND
  Cast([Time].CurrentHierarchyMember.Name as string) MATCHES "NEW PROJECT CATEGORY NAME.*"
THEN
  1

Figure 2

ACTIVITY 3: Add Custom Members to the Time Dimension for the PI Based Reports

  1. Check the program's confluence space and get the Start and End Dates
  2. Verify the dates are correct with the RTE or Program Manager for the current and upcoming 5 PI's
  3. Add the Program key, PI numbers, and Start and End dates to this page
  4. In a 

    dashboard report using the time dimension

    , expand the dimension
  5. At the bottom of the report, select "Define new calculated member"(fig. 3)
  6. For the PI date range members, enter the name at the top of the dialogue(fig. 4), using the following format: Jira Project Key-PI PI Number. The hyphen is necessary for some reports to work properly.
    1. Add the code with the start end end dates that correspond with the PI number:
      Aggregate(
      [Time].[Day].DateMembersBetween('Jan 19 2022 00:01','Apr 19 2022 23:59')
      )
    2. The use the full timestamp shown above. The hours and minutes are critical
  7. Select the update button to save the calculated member to the dimension (fig. 4), and it will appear in the list of members of the dimension
  8. Repeat for the subsequent program's upcoming PI's
  9. For the PI Start Date members, enter the name, using the following format: Jira Project Key PI PI Number. Note the absence of the hyphen
  10. Enter the code with the date corresponding to the start of the PI number, in the following format:
    [Time].[Day].DateMember('Oct 13 2021')
  11. Save the calculated member to the dimension (fig. 5), and it will appear at the bottom of the list of members in the dimension. *note: you will only need to create these once, and they will be available for use in any report with the time dimension
  12. Repeat for the subsequent program's upcoming PI's



Image Modified

Figure 3


Image Modified

Figure 4

Image Modified

                     Figure 5



 
 

Activity 4: Add Program specific feature statuses to user defined measures and custom members

  1. Identify Program Statuses
    1. Confirm the correct program project and program board with the Program's RTE or Program Manager.
    2. Navigate to the program's PI board in Jira, and select the carat on the "Board" Button, and select "Configure"
    3. Select Columns
    4. Note which statuses are mapped to columns
  2. Add the correct statuses to reports using status
    1. For the "Current Program Backlog Health", "Features in Status on PI Start Dates", "Features Started and Closed Per PI", and "Feature Cumulative Flow" reports using status, bookmark and select the appropriate statuses identified in step 1 to the report in the "Status" or "Transition Status" Dimensions. (fig 6) Note that in the "Current Program Backlog Health" report, no in progress statuses are used.

Figure 6

Activity 5: Add "Complete" statuses to Jira Data import


  1. Navigate to the source data tab in eazybi and select "edit" next to the Jira Cube Import
  2. Scroll down the Statuses and History section (fig. 7)
  3. Add any program specific "completed" statuses to the Closed Statuses field needed. 


Figure 7




Activity #Suggested or Potential Workaround(s)
1Create a policy for RTEs or Program Managers to submit requests to remove and add teams as they are created or decommissioned
1Create an "active" flag in Jira at the project level and add it as a property or dimension so that inactive projects and project data are not imported
1Let inactive programs screw up data, and let program leaders face the consequences
































...