The issue data itself is pulled from the indexes with the new boards, rather than from the database directly, so this should greatly improve the load times you'll see on larger boards. Additionally, your Jira instance will need to pull up the data about these issues at each refresh - if there's a thousand issues there and 25 people want to load this board at the same time, then there's a bit of work to be done there. Additionally, it can be difficult to find the issues you want in a sea of cards. Boards that have 500 or more issues to display will take a longer time to render in some browsers (IE8 for example) or on lower powered machines (see the bottom section on Client Side Considerations for more info). It's important to note that while boards can display up to 2,000 issues, it's not recommended to be viewing that many records on the board at once. Whenever you create a new board using the Scum or Kanban presets, a corresponding filter will be created for you as well - this means you can modify the filter to narrow down the issues on the board, removing those you don't need to see and letting you focus on only what you need. Keep in mind, you can create multiple boards (even multiple boards that cover the same issues) to show data differently for different teams. Generally it's best to start off thinking about the true goals of this board. Not only can you include issues from multiple projects, but you can also exclude issues based on JQL - this can lead to confusion of what is and is not appearing on the board. There are a number of things to keep in mind when configuring boards for scale.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |