-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
-
None
-
None
It's great having the plan mode when adding items to a sprint; but, I need the ability to directly add an item to a sprint upon creation. The issue is that when testing, the team will find bugs that need to be fixed during the development sprint. But, they don't automatically get added to a sprint; you have to go back to the plan mode and add them into the sprint. The latter isn't efficient since you need to be an administrator for managing the sprints and not appropriate for all QAs and Devs to have. The PO should not have to be involved in every decision regarding bugs identified during unit and functional testing.
If you add them now via JIRA, they actually don't get captured correctly and your reporting on the issues found during that sprint are not valid. You also easily lose sight of them as they don't appear on your board.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-8178] As a user, I need to be able to set the sprint when creating an issue in JIRA
exposure of the exact same 'Send To' options as on plan board would cover it..
It would also be awesome to set the spring when starting the issue - not as a standard workflow, but as a safety measure to not work on issues outside the running sprint.
Jan Swaelens
added a comment - We would also really like this feature. Navigating to the plan board each time simply takes too much time and becomes quite cumbersome when a lot of issues exist in the backlog.
Jan Swaelens
added a comment - We would also really like this feature. Navigating to the plan board each time simply takes too much time and becomes quite cumbersome when a lot of issues exist in the backlog. 
Paul Brown
added a comment - Hi,
I'd also like to see this feature being supported.
The main use case we have for this is that during a sprint, QA wish to raise an issue which needs to be resolved within the sprint. At present issues are placed in the backlog and this doesn't help us monitor the deliveries completeness for the sprint.
A drop down list which allows the sprint to be selected would resolve this issue.
Thanks
Paul
Paul Brown
added a comment - Hi,
I'd also like to see this feature being supported.
The main use case we have for this is that during a sprint, QA wish to raise an issue which needs to be resolved within the sprint. At present issues are placed in the backlog and this doesn't help us monitor the deliveries completeness for the sprint.
A drop down list which allows the sprint to be selected would resolve this issue.
Thanks
Paul 
Steve Rice
added a comment - This slows us down significantly when doing our sprint planning. Many of the teams at our company are complaining about this.
Steve Rice
added a comment - This slows us down significantly when doing our sprint planning. Many of the teams at our company are complaining about this. 
Karie Kelly
added a comment - The specific issue is one reason why we use JIRA/GH for planning purposes, but cannot actually use for actual sprint work. We have to move all sprint issues into TFS and the engr and QA teams work in TFS. Why? Because the QA team can add bugs directly to the iteration path that is associated with the sprint and the developers know about them and can pick them up to work on them. The product owner has to keep up with the story's progress in GH so that we can keep a good burn down. But, as you can see, it is not timely (depends on when the data is synchronized), and inefficient.
Karie Kelly
added a comment - The specific issue is one reason why we use JIRA/GH for planning purposes, but cannot actually use for actual sprint work. We have to move all sprint issues into TFS and the engr and QA teams work in TFS. Why? Because the QA team can add bugs directly to the iteration path that is associated with the sprint and the developers know about them and can pick them up to work on them. The product owner has to keep up with the story's progress in GH so that we can keep a good burn down. But, as you can see, it is not timely (depends on when the data is synchronized), and inefficient. 
Oliver Gierke
added a comment - Ahh, okay. Good to know. That was true for my case here. I was just looking for a quick way to directly add tickets to Sprints while planning them, which is what I seem to have discovered. Not sure the hardcore agile people allow you to add tickets to a sprint once it has been started 
.
Oliver Gierke
added a comment - Ahh, okay. Good to know. That was true for my case here. I was just looking for a quick way to directly add tickets to Sprints while planning them, which is what I seem to have discovered. Not sure the hardcore agile people allow you to add tickets to a sprint once it has been started . I've noticed, that if you use the "Create issue" button on the Sprint planning page, the issue created automatically gets added to the current Sprint in planning. That might not be sufficient for all of the described use cases here but so far I have created the issues from the project pages, and then had to look them up and assign them in a further step in the Sprint planning view.
That's only true if the sprint has not yet been started yet.
Many thanks for reporting this issue. This functionality has been implemented as of the latest version of JIRA Agile.
Regards,
JIRA Agile Team