FAQs: Get Answers
Find Comprehensive Solutions to your Common Queries
Browse this sectionModules / Planning
Frequently Asked Questions
If you don't see an answer to your question, you can use the search option, feature documentation or ask your question using GitHub discussions. You can also contact us via mail, if none of the above option helps.
Open Planning > Sprint Planner from the menu and choose a board in the toolbar. A board is one team. Open Team to set up the members, their allocation, hours per day and working days, then use the Sprint board view to drag issues between the backlog and sprints. In the Jira Cloud app, the planner is also available as the "Sprint Planner" page in the sidebar of a Jira project.
Capacity of a member = working days in the sprint x hours per day x allocation to the team - leave - holidays. The capacity override of the sprint and the focus factor of the team are then applied. Points capacity uses the selected velocity scaled by the available capacity, or the hours per story point when there is no velocity yet. Check the allocation, hours per day, working days and leave of the member under Team and in the Leave view.
Yes. Open Team > Leave calendars and add a calendar source: Outlook, Google, an .ics file or Confluence Team Calendars. Choose whether the calendar holds the leave of each person or the holidays for the team, and which events count (keywords in the title or category, only all-day events, or the availability shown for the event). Calendar people that are not matched to a team member can be mapped once and the mapping is kept. Only the matched leave (person, dates and hours) is stored, never the whole calendar.
By default, moves and edits made in the Sprint Planner are written to Jira immediately. Turn on Draft mode in the toolbar to stage moves, edits, plans and dependencies without writing to Jira. Apply writes all the pending changes and reports the result of each, and Discard restores the board. You can choose in the settings whether the planner opens in draft mode.
Team settings and calendar sources are saved as properties of the board, and planned segments as properties of each issue, so everyone planning with the board sees the same data. In the Jira Cloud app, leave is kept in the app storage of your Jira site. In the browser extension, web and desktop versions, leave is saved on the board. As this data can be read by anyone who can view the board or the issue, the planner asks you to accept a note first; until you accept, you can view everything but nothing is saved. Leave older than about 13 months is removed automatically.
Program Planner plans the work of several teams together for a quarter or a Program Increment (PI), with a program board, capacity per team and iteration, dependencies, objectives, risks and confidence votes. It is available only in the Jira Assistant app for Jira Cloud, under Planning > Program Planner, because plans are kept in the app storage of your Jira site. SAFe terminology can be turned on in the program settings.