For our Stories, for the default workflow we have is Draft > Planned > In Progress > Done. We have other states but those are the key ones. Draft is defined as a new Story to schedule. Planned is defined as a Story that has been scheduled in a sprint. In Progress is defined as a Story being worked on currently. And Done is defined a completed Story.
Right now we have Sprint as a mandatory field when moving from Draft to Planned. Which works, but we would much rather have a Story moved into a sprint in the Scrum board and not while editing an issue. Which we can do, but we are hoping there is a way that adding a Story into a sprint will automatically trigger a status change as well. From Draft to Planned. Is it possible to trigger a transition once a Story has been added into a Sprint?
I am not necessarily answering the question asked here but it sounds strange to me that you would want to do that. I assume that the goal here is to make sure that stories are ready to be executed into a sprint? The Draft > Planned > In Progress > Done workflow sounds good for a KanBan where no sprints are defined but you seem to be using Scrum.
What I do is that when I groom my backlog and that I feel a story is ready to be executed, I add a label "READY-ready" to it. I have also some quick filters allowing me to zoom in on stories that are not "READY-ready" so that they can be caught before starting the sprint during backlog grooming sessions. So before starting the sprint, you activate the quick filter and see if some stories in the sprint are not yet ready and you could even flag them in the board.
If you are really looking for a hardcore way of doing it while still using your workflow, you could use an add-on such as Checklist (shameless plug here ). Use the checklist to list the items of your definition of ready and prevent the workflow transition to Planned until all items in the definition of ready are not completed.
If none of this satisfies you, then I think that you only solution would be to write a plugin for that as I don't think you will find this functionality out of the box.
Okay. Thanks for the response.
My preference would be to just remove the Planned status. And then only move from Draft to In Progress. And have the action of assigning an issue into a Sprint corresponding to saying it is Planned. So Draft + No Sprint assigned = Not Planned. Draft + Spring Assigned = Planned.
I took a look at the possible options and this is what I found:
Potential Solutions (current / future)
What I surmised is from this is as @Yves Riel suggested keeping issues in their current status is the best solution. An issue may be worked on in multiple sprints meaning it could already be "in progress" when added to the sprint. As I've read, sprints are a way to plan what you work on, and shouldn't necessarily affect the status of an issue.
If anything, upon adding to a sprint, the "Assignee" field could be requested as typically that is the time that issues are assigned anyway. You might be able to Associating a screen with an issue operation to do this.
I recently did this using a Scriptrunner script listener and I thought it might be valuable to share the details for anyone searching for this answer in the future. My use case was changing the issue to "In Progress" if it was added to a Sprint.
In Administration | Add-ons | Scriptrunner | Script Listeners | Listeners, I created a Fast-track transition.
Fields and values were as follows.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs