What happened to the parent-child issue link type in JIRA?
Is there a better way to establish parent-child relationships than adding back in a custom issue type for parent-child? I haven't used JIRA since before Scrum and Kanban boards were introduced, so guessing this functionality has been swallowed up by Epics or some other functionality.
Example: I create an issue for a feature called "Ability to Attach a Photo". Then a create issues for "Ability to Attach a Photo using Camera Roll", "Ability to Attach Photo using Camera", "Ability to Attach a Photo using...". I don't want to create them as sub-tasks because they are independent features on their own and we don't have to complete every single one in the same sprint. In the end, "Ability to Attach a Photo" will not have any work logged against it directly, the work logged will be the sum of the child issues.
So none of these solutions are really good. Any suggestions would be extremely appreciated!
Old school, dude! I'd use JIRA Agile and Epics. The Epic Link field shows the related issues which can be from any project. Or just use an existing link type such as Relates. The parent child issue link may well have been a custom one someone created locally, I don't recall it being a standard one. Keep tweeting those runs!
Hi Matt, Yes, old school! Been forced to use Pivotal Tracker recently and helping someone get started with JIRA. Your answer is what I was afraid. I can feel the Epics going from a few dozen to a few hundred. From Atlassian's documentation at https://confluence.atlassian.com/display/AGILE/Working+with+Epics, "An epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories." In the scenario above (which is just one of many), we essentially have a small user story, not a large one. I'm worried that Epics will lost their effectiveness once there are that many of them and they become less distinguishable from stories. So for small user stories such as attaching a photo to a post, we'll see how Epics work, and if that doesn't work out then we'll add in a parent-child issue link. Thanks for answering and hope all is well at ServiceRocket!
I think you will just need to recreated the Issue Link (https://confluence.atlassian.com/display/JIRA/Linking+Issues). Sub-task should work also but they are of course considered "sub-task" type and not the same level as a "parent".
Hi Timothy, I responded about sub-tasks above, not gonna work because I want to assign to different sprints. As far as re-creating the parent-child issue link I had listed that as Option 2 above. If that's the best way, and I'm guessing I'm not the only one in this predicament, then why would Atlassian have removed this issue link in the first place?
Since it used to be there by default and it is no longer there, I am guessing it was removed - not because it was not utilized by users - but because a better way to establish parent-child relationships was implemented. Atlassian doesn't remove a default option like that without careful scrutiny. The only thing I can think they added to replace it would be Epics (sub-tasks have always been there and don't allow for sub-tasks of the same parent to be assigned to different sprints), but then we'd go from 2 dozen epics to hundreds.
Hi Jim, I just updated my question with one more option. "I could make each of the child issues sub-tasks, but then they are directly tied to the parent, and I can't assign them to separate sprints. I'd like to implement "Ability to Attach a Photo using Camera Roll" and "Ability to Attach a Photo using Camera" first, and then additional options in a later sprint." So sub-tasks doesn't work for me in this case. Thanks for answering!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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