Discussions
-
How the Auto-scheduler handles capacity for Kanban teams
This article focuses on how the Auto-scheduler in Kanban Plans handles capacity based on the capacity distribution algorithm. For a more holistic view of the Auto-scheduler, please see the following resources: * How does the Auto-scheduler in my plan work? * Capacity in scrum vs. kanban teams in your plan Advanced…
-
Include subtasks not including...
Jira's Time tracking functionality allows users to Log time on an issue which then translates to Time spent or work logged using the units of weeks, days, hours and minutes. This value is paired with the Original Estimate and the Remaining Estimate field that is dynamically calculated using a formula of {Original - Logged…
-
Issues appearing in the Unassigned swimlane when Grouping by...
When viewing work in Advanced Roadmaps, the View settings menu lets you customize how issues and related information are displayed on your timeline. By using the Group by Assignee, Release, Sprint or Team, each group will be allocated a swimlane containing assigned issues. Any unassigned issues will be in…
-
Why can't I manage my Sprint while I am the SCRUM Master?
As a SCRUM Master, one of your key tasks involves planning Sprints in your team and in order to do this, you must be able to create new Sprints and complete active ones. In order to fulfil these tasks as a SCRUM Master, you require the Manage Sprints permission which is configured on a Project level in its Permission…
-
Something went wrong in Google Chrome
Some Atlassian account users may experience that they're unable to access their Profile page with Google Chrome. Instead, they are directed towards an error page with a Something went wrong message. How am I able to determine that this issue is local (DNS, browser, network, firewall, etc..) There are several checks you can…
-
Knowing when you have a Shared Sprint
When using parallel Sprints in JIRA Software, you're able to run multiple active Sprints simultaneously. Often enough when working with multiple Sprints, they can sometimes get mixed up and create what is known as a "Shared Sprint". Sprints aren't dependent on any Board or Project meaning they are not bound to the Board…