Hi Team,
Been experimenting with a few different setups, and don't want to keep jerking the teams around in different directions.
We have a handful of different engineering team projects/boards (Teams 1-5). We have a consolidated QA department that has its separate Kanban board. These Team boards feed into the QA Kanban board and vice versa; when a story fails testing on the QA board for instance, it punts back over in "To Do" for the development team.
I recently got 'red-balled' into the Next-Gen projects, due to the roadmap feature. The teams, really like that roadmap feature, as it adds a sense of stability and expectation. However, workflows aren't ready for the Next-Gen boards, and judging by Jillian's comments here: https://jira.atlassian.com/browse/JSWCLOUD-17434; they won't be ready for some time (cross-project).
I'm familiar with Automation for JIRA plugin, but it can't move issues from one board to another, and cloning / deleting the old one gets janky very quickly, as you can't even tell which project an issue is from, since it was cloned in the QA project.
At this point, I'm completely open to suggestions; I need a solution. Requirements:
Hope that makes sense.
I think the responses are going to be "You messed up, go back to the classic projects and use a different roadmap tool". I'm totally willing to bite that bullet if necessary. Just gauging the community before I do.
Thanks in advance!
Charlie
I was thinking the first response was going to be a link to a $10.00 a month solution. Seems like every time I hit a wall and search for a solution that is the answer. I have been "trying" to switch from MS Project to Jira Software and its painful thus far. At the point now of trying to determine how to manage and link the QA tasks. Hopefully something will come up on this thread or another.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.