I am new to the products because I am performing an evaluation. I apologize if I am user the wrong terms to describe my need. I have a need to establish and track dependencies from a user story (US)in one project to another one in a different project. We have many projects in flight at one time.
Is there a demo / walk through that is available that will show me how this is done?
I saw some discussion about dependencies between Epics. I want to focus on the US for now.
I believe that you can take a look on this page from our documentation to accomplish this, as it details how to have a board showing stories from multiple projects (and, thus, creating some kind of dependency as you may note).
-- Arthur Gonçalves
Interesting, You use the "linking" feature now.
Do you have something that shows the Predecessor and Successor on the same row.
Maybe something like this?
|Predecessor Project||Predecessor Story||Story State||Release Date||Iteration End Date|||||||Successor Project||Successor Story||Story State||Release Date||Iteration End Date|
JIRA may have the ability to extract this information, and there may be plug-ins that enable filters to obtain information on linked issues, release dates, and sprint end dates from JIRA.
Release dates are managed through fixVersions and we use a code name to designate a release.
Iterations and iteration end dates are managed through the Agile Boards; we use the Sprint identifier, e.g. ProjectNameSprint99 to signify the iteration. The team is aware of iteration start and end dates.
Story state is available from JIRA.
For an issue, project ABC, number 123: ABC-123 would be linked to ABC-144 (typically we used "blocked by" or "relates to" or "duplicates" which may be a customisation of the standard implemenation). It provides visibility of dependencies on an issue by issue basis.
"Blocked by" is too heavy a hammer for dependencies for us. For us it means "I'm working on a story in the current sprint and I'm blocked by ..." Similar to using a red "Blocked" label in Trello and tagging cards with it.
Dependencies describe an order in which things need to done. At a minimum I want, when I try to drag a story (or task) x into a sprint and story x depends story y being "Done", I'm told that I can't do that before story y is done. And if I try to drag story y above story x in the backlog, I can't do that either. It's deviation from pure Agile where the relative order of cards in the Backlog is assumed to tell the whole story.
We'd be happy with "Depends on" as a type of issue link if it came along with "you can't do that" as described above. We do think some about dependencies when prioritizing the backlog up front before we start sprinting.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot