well... i dont think its nonesense, i have Android and iOS projects where there is some shared code, i'd like to have the shared code as a subtask with two feature issue parents.
is there another better way to do it? (keep in mind the subtask is too small to be a feature issue that blocks other issues, and the two feature issues are too big to be combined as one.
I'm afraid when it comes to logical breakdowns of work, it does not make sense to have a sub-task have two parent issues. They're supposed to be there to break up the parent, which they can't do if they are part of another.
The best way to handle it is two sub-tasks, and link them together with an issue link.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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