Hey all!
Below is the Q&A from a Jira Plans session I ran on September 2nd over with Atlassian Learning public classes (def go check those out if you're looking for a wide range of free live training).
Curious what other question on plans you have, or how you can help me answer them better!
Answer - Default is hours; however, you can configure/select story points (SP) instead depending on the team configuration (e.g. they have sprints configured).
Answer - Jira Plans in Cloud is the evolution of the feature previously known as "Advanced Roadmaps" in Data Center (DC).
Answer - Yes, you can filter by link type within the plan settings and view settings. Filtering only shows links that exist in the plan, so if one is missing, none of the work types in the plan use that.
Answer - No, Jira requires selecting at least one space, board, or filter because it needs an explicitly defined source of work items to pull into the plan.
Answer - Dates are not mandatory at the field level to create a plan, but without dates, items will not generate timeline bars. You must add start/due dates (or use auto-scheduling based on sprint dates) to visualize a timeline.
Answer - This is a known browser/cloud cache behavior where open sessions do not auto-update dynamically; users currently viewing the plan must refresh their browser screen to pull the updated view settings.
Answer - I don't believe so. Jira Align can push/pull some info from Jira, but I don't believe Align-specific fields can be pushed down.
Answer - Yes, Rovo can read the plan via the Teamwork Graph and perform actions like creating work items directly within a connected space from the chat panel. Specific pre-built out-of-the-box Rovo Agents dedicated solely to Jira Plans do not exist yet, though custom skills/actions can interact with plans.
Rob Hean
0 comments