For our use case, we need a custom Task that can be a child of a Story task, or completely independent. The only way it currently seems possible is to create the same custom task at the Task and Sub-Task level, but we're looking to avoid that duplication.
Hi @Nick Tymeson - Did you get your question answered?
welcome to the community!
Would it be possible for you to "move up" the native Jira issue hierarchy by one level, to the Epic level? Stories (or Tasks, etc.) *can* be part of an Epic, but don't have to be.
If you want to stay on the Story/Task level, you'll have to work with issue links, e.g. model a "is parent of"/"is child of" issue link.
Hope this helps,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to add to the above: There are apps in the Marketplace that allow showing such relationships as hierarchies and make it easier to create issues "within" such a hierarchy. E.g., here's how this looks in JXL for Jira, the app that I'm working on:
(The clip shows Bugs in a "is child of" issue link relationship to tasks, but you can model any scenario.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I created the custom linked issue type 'is a child of', however it doesn't look like Jira recognizes that the same way it recognizes the parent/child relationship of a story task to a sub-task. We'd like to stay on the story/task level. Linked issues appear as outwardIssues/inwardIssues. Regardless of naming conventions for custom linked issue types, it appears this will always be the case for how they're referenced.
I'd like to avoid Marketplace apps due to costs with a high number of active users. Is this not supported out-of-box?
I appreciate your feedback.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you're correct regarding issue links - Jira doesn't "natively" understand them as parent/child relationships; for Jira, they could be _any_ connection between two issues. I'm not aware of an out-of-box solution, unfortunately.
Regarding apps, I understand your concerns. You can always do a free trial and form an opinion on an app first. If you'd like to chat more, just drop me a mail at hannes at fine dot software!
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.