Define link type(s) that will be set automatically when creating subissues or changing hierarchy
Define link type(s) that will be set automatically when creating subissues or changing hierarchy
LInks synchronization done in 0.4. Quick steps: open “Manage Structures”, click “Settings” in Synchronization column and add “Issue Links” synchronizer. Make sure to read through warning messages.
This does not cover GH interoperability (Epic/Theme is a label, not a link, isn’t it?) and it doesn’t address creating an issue of different Type – it’s a different improvement, also planned.
-
Sebastian, thanks! We've got that in mind.
In the current version, if you already have a Task under a Story, you can select the Task and hit Enter to create a next task under the Story.
Igor
-
Sebastian Zakłada commented
As a quick addition it would help if you just allowed to create Sub-Issues of a different type than its parent's one. For example, if I want to create a Task under the Story, the tool creates a sub-linked Story instead. I have to edit it each time to just change to the Task type and it is cumbersome.
-
Walter, thanks for the explanation! That makes sense, and I can see that feature a bit farther down the road (as well as restrictions/rules for some fields based on the hierarchy, like the types relationships you describe), probably in a version that follows the first release.
-
Walter commented
1. Allows for interoperability with other plugins displaying hierarchy/matrix structures that depend on certain links (such as the recent https://studio.plugins.atlassian.com/wiki/display/JIRAGANTT/Home , the Hierarchy report from Pixies, the Issue links Matrix plugin, SynapseRT plugin,..). Would be nice to see that structures and links can work together (not only co-exist).
2. Interoperability with GH -> Quickly create stories from an Epic/Theme. This would allow to keep the GH link types and all the GH functionality. Come to think of it ...you should then also be able to define what the default issue type is for a subissue (e.g. default issuetype for an Epic would then be a Story). But that's in fact another request/idea....this would then also allow to quickly create bug issuetypes from a testcase issuetype...aaarggh the shear potential of this plugin!!
4. In some cases it could also be desirable to be able to define a predecessor/successor order for the issues created through the structure plugin (e.g. issues on same level must be solved in the order displayed, each issue blocks the successors, I think you can also set this as default behaviour in MSProjec). These could be done by also creating links.
-
Could you please elaborate, what you need that for? The structure plugin shows a Structure section for each issue where its parents and children are clearly visible.