Settings for using sprint dates when issues don’t have target dates Feature enhancements
We’re now giving you that extra level of control over your data, and letting you choose whether or not these sprint dates should be used as issue dates in the plan. Previously, if an issue didn’t have target dates, but was assigned to a sprint, the issue would automatically inherit the sprint dates for its start and end dates in the plan. Sample issues filtered by assignee Sprint date configuration This can help you see how much work someone in your team is taking on, and quickly shuffle work around if need be. You can now filter for issues assigned to specific users in a plan. Issues sorted by ascending target start dates New assignee filter This helps you quickly find and organize issues with upcoming start dates or deadlines.Īs this is our first iteration at issue sorting, let us know how you’d typically sort issues by clicking the give feedback button in your plan. You can now sort issues in a plan by target start dates or target end dates, in ascending or descending order. This helps you monitor how much work your Kanban teams take on each week, and ultimately helps you distribute work more effectively.Ĭapacity details for a Kanban iteration Sorting issues in a plan You can now view more capacity details for Kanban iterations, like the number of hours that have been completed against the team’s weekly capacity. Portfolio for Jira Server team More capacity details in Kanban Learn more about our latest platform release, and check out this article if you have any pressing questions about the new plans! Upgrade now to plan work for your teams more efficiently in Portfolio for Jira.
Renew your active software maintenance now. We’re pleased to announce the release of Portfolio for Jira 3.8.
0 kommentar(er)
