Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Simple answer is that is not possible as Task and Story sit at the same level. What you could do though is use Advanced Roadmaps in JIRA and have initiatives as issue types which sit above Epics.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Parabéns, muito próximo do Guia Scrum...leitura rápida, conteúdo de simples entendimento ...irei levar o artigo como uma colinha para utilizar nas inclusões de demandas no JIRA..
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
We are using Jira for software development and we have customer support also using another tool. When customer support raises a problem, it takes time to assess the problem before something is classified as a bug or maybe a change request story etc. what’s the best way to track these problems raised to us before they become bugs or stories ?
When explaining issue types to users, I explain that an issue type is a different type of work, and there are only 3 types of work in the universe:
1. story: making something better than it is;
2. defect: fixing something that's fallen below what it should be; and
3. task or doing something which is neither story nor defect but has to be done to achieve the overall goal).
The rest is just "grouping".
I use an analogy of putting up some new shelves. Putting up the shelves is the story/improvement/new feature (it's all basically the same). Buying a drill is a task. Fixing the mess you made putting up the shelves is the defect. You can group issue types together [into epics] but it's just a grouping and you can group epics together into an Initiative which is still just a grouping. A child issue (sub-task or anything else) is just an issue that is split out of the parent but remains an intrinsic part of the parent. Otherwise it's a separate but linked issue.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Hi @Christina Nelson, thanks for your posts! The content is well-organized and goes straight to the purpose. I just have one concern that has not been mentioned in your post: The definition of Feature Development type in Jira. What is the difference between User story/Feature Development/Task? Does it the sub-type of User story?
64 comments