how to have dependency between stories ?
I tried linking the stories, but need to have option of dependency so i can see which story need to be completed before we start other.
i can see which story need to be completed before we start other.
The Links Hierarchy add-on displays the full hierarchy of Stories on a nice interactive tree, so you can expand and collapse children issues and sub-tasks.
Each issue/sub-task shows an icon with the Sprint status (,
,
), so you can visually inspect what belongs to Sprints not yet closed:
Once all the children issues and sub-tasks show the sprint completedicon, you know all the Story has been fulle completed. Moreover, you can also hide all the Resolved issues automatically and then see what is still pending under the Story.
By using those both features you can easily track the full Story hierarchy state.
Commercial, but not too much expensive, I would say.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can make use of issue linking. Once you link the issues, you can find it on the issue details.
You can also search based on the links either using standard JIRA query to get issues linked to a given issue key or using add ons like JQL Tricks plugin to display all issues with a certain link type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand that point because I have heard it before. You will have to write a custom workflow condition to prevent closing of issues based on the status of linked issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i tried link option but i am able to close the story which is still dependent on the story which is open.
I want it to be able to block the story from closing before the blocker is closed. so true dependency is required.
Thanks for your earlier reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jobin Kuruvilla [Adaptavist] Does that mean that 'dependencies' in the conventional project management sense, e.g. Task A must be compelte before Task B can be started, is not possible in Jira.
Hence, your suggestion of using custom workflow's is the advised work-around?
Ty,
O.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.