1- What do you do to issues that need to be carried over to next sprint on Jira? Pull them in the next sprint log or create new stories? How can one track and know in how many sprints the story was built in? 2- Some columns on my active board, I can't pull issues or glitches under them (I have previously worked on the workflow and it was working fine, not sure if someone from the team made any changes). How can add "Categories" on the workflow (if this solves the issue) 3- Jira stories can be moved one status forward only (on my active board). Please can you advise why?
1. Work that moves from one sprint to the other never generates new work items. It either goes already to the next sprint (because I want to continue to work on it) or it goes to the backlog, to be planned for a future sprint (not the next one). The field Sprint will always show you the current sprint + previous sprints where the item has been assigned to. 2. Some statuses can only be assigned to by the person who reported the issue or the person who is working on it. 3. Usually, I prefer to have one step at a time as it will make less likely to make mistakes (practical experience) and makes the workflow much clearer (in my opinion). But, like I mentioned in the video, you can (and should) make sure you adapt them to your agile reality. This means that you only need to configure additional links between the statuses you would like to "travel" in between.
@coachsondberg, thanks a lot for taking the time to see and comment. What you suggest can indeed be a possible option. However, having a cancelled item classified with DONE will mean that JIRA will consider it DONE and will credit the estimated points as velocity. This happens because the DONE status is in the last column of a scrum board and it's how JIRA finds which items are actually done. Crediting a team points for a Cancelled item is definitely something that we don't want :) The Cancelled status allows me to leave all those items outside the board, since they don't bring any additional value in that board.
This set of workflows is demonstrated masterfully! Thank you for posting. I look forward to going through your other guides.
Thanks a lot Aaron. Really happy that it was useful! I'll keep delivering them :)
@Brayden Marshall yea, I've been watching on instaflixxer for years myself :)
1- What do you do to issues that need to be carried over to next sprint on Jira? Pull them in the next sprint log or create new stories? How can one track and know in how many sprints the story was built in?
2- Some columns on my active board, I can't pull issues or glitches under them (I have previously worked on the workflow and it was working fine, not sure if someone from the team made any changes). How can add "Categories" on the workflow (if this solves the issue)
3- Jira stories can be moved one status forward only (on my active board). Please can you advise why?
1. Work that moves from one sprint to the other never generates new work items. It either goes already to the next sprint (because I want to continue to work on it) or it goes to the backlog, to be planned for a future sprint (not the next one). The field Sprint will always show you the current sprint + previous sprints where the item has been assigned to.
2. Some statuses can only be assigned to by the person who reported the issue or the person who is working on it.
3. Usually, I prefer to have one step at a time as it will make less likely to make mistakes (practical experience) and makes the workflow much clearer (in my opinion). But, like I mentioned in the video, you can (and should) make sure you adapt them to your agile reality. This means that you only need to configure additional links between the statuses you would like to "travel" in between.
Beautiful Lecture.
Many thanks!
I´d argue the cancelled state is redundant - it might as well be simplfied to being "done" with the resolution "wont do" or similar
@coachsondberg, thanks a lot for taking the time to see and comment.
What you suggest can indeed be a possible option. However, having a cancelled item classified with DONE will mean that JIRA will consider it DONE and will credit the estimated points as velocity. This happens because the DONE status is in the last column of a scrum board and it's how JIRA finds which items are actually done. Crediting a team points for a Cancelled item is definitely something that we don't want :)
The Cancelled status allows me to leave all those items outside the board, since they don't bring any additional value in that board.
@@palhinhas yeah ok, you could still go deep dive under the hood and set it up, but if we are talking out of the box functionality, youre ofc right!