Hi Team,
We have recently migrated some Trello projects across to Jira. In doing so, all of the columns have migrated as "To Do" type statuses which has resulted in being unable to see new issues on the board as we are over the issue limit.
The problem is that even after changing some of these columns/statuses to "Done" type statuses, we still can't see new issues on the board.
Is this expected behaviour or is there something else we need to do here?
Thanks,
Mia
Hello @Mia Bright
One feature of Business/Work Management boards is that items that have been "done" for 2 weeks or longer will automatically be hidden from view on the board. Does that explain any of your missing issues?
Beyond that it appears that there is a limit on such projects' boards to display only the first 3000 issues added to the project (excluding subtasks), as documented in the change request where the limit was increased from the previous limit of 1000.
https://jira.atlassian.com/browse/JWMCLOUD-23
There is a new change request linked to that one asking for there to be no limit.
https://jira.atlassian.com/browse/JWMCLOUD-613
The current work-around is to create a Software Kanban board based on a saved filter that references the Business project. Software Kanban boards have an issue limit of 5000.
Hi Trudy,
In regards to your first question, there is no issue with them being hidden after being "done" for 2 weeks or longer. It's that I would expect any "done" issues to stop counting towards the issue limit.
I would also expect to be able to filter to see these issues. It is quite frustrating to not be able to put any filters or views on the board to be able to retrieve these "new" issues if we are over the limit.
e.g. as Business Projects have different views per workflow, I should be able to see 3000 issues per view as opposed to in the project as a whole.
Thanks,
Mia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Regarding the hiding of "done" issues, it just came to my attention that yesterday Atlassian released a change to make this configurable in both Company Managed and Team Managed Business projects with the available options being 7, 14, 30, and 60 days.
https://jira.atlassian.com/browse/JWMCLOUD-19
As just another user of the product I am sympathetic to your frustration. I recommend that you contact Atlassian directly through a support case to see if they can offer you any additional information about change requests related to the issue limit functionality.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know that I can adjust the dates but it still gives me a minimum 7 days until the issues drop off where I can't see any new issues. Super frustrating to not be able to even filter down to less than 3,000. I will have a chat to them and see if there is a better workaround than creating a whole new project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For clarity, the workaround of creating a second board (a software-type kanban board) based on a saved filter does not require creating a new project. You create a filter to select the issues you want from the Business project, then create a board based on the saved filter.
Two articles discuss this methodology:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
Boards still have to be nested somewhere so it would require a new project to house it. I know there is the option to create a personal board but as this is a non-technical team's project it is not feasible to expect them to all go in and set up and then administer their own boards.
Thanks,
Mia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could add the board as a Personal board.
If you didn't want to have the board associated to a user that might leave, you could set up a "service" user account to which the board could be associated.
You could also share the filter with the JWM Project, and use the Add Shortcut option in the JWM project to add a link to the board so that they would not have to hunt for it.
You could also add other users, from the project, as administrators of the board and editors of the saved filter.
I agree that it is not an ideal solution for a non-technical team. I am only pointing out the options that currently exist. I do think your feedback is entirely valid and should be given to the Atlassian team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.