A stretch user story is something that we plan and call as stretch in the beginning of the sprint.
I dont want it to remain in the backlog and later include it, as that would be shown as a scope creep in the burndown. Please help me understand, how to solve this problem using JIRA.
You need to set up some way to identify the story (I'd create a new issue type of "stretch story", but you could do it with fields), then change the board filter so that it excludes it from the sprint based on the flag you've chosen (e.g. and issuetype is not "stretch story")
Thanks for the reply. If the this new issue type using filter is excluded from the sprint then it takes care of not counting it in the committed velocity. However, if it does get completed in the sprint then we want it to be counted in the actual velocity for that sprint. If you change its type from 'stretch story' to 'user story' then it will cause scope change. Thoughts?
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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