2 - 3 : Indeed configuration per structure level (on Edit Structure) : *this* structure is available to <list of types>.
4 : Only nice to have : but if cookie implementation remains in the future then you could add logic that changes cookie info for
* changing the order of the structures in the "select" box
* to indicate this is the default structure for the current issue type
* to indicate this is the default filter for the current structure
But only nice to have.
1. When no structure is available for the user (e.g. no view rights are defined for his role) => do not show the 'structure section' (as this can be confusing). This the follows the same logic as subtasks/links where the sections are not visible if no subtasks/links are available.
2. Define for which issuetype the structure is available/not available.
As you can now create multiple structures (which is great btw!) you can start linking structures to certain issue types
3. Define which issuetypes shows the 'structure' section and which don't.
(can be implemented by the combining the above 2 features)
4. Define the default structure for an issue (when multiple structures can be consulted)
More or less the same functionality as exists in the LNIO plugin. See image https://plugins.atlassian.com/server/1.0/screenshot/fetch/11746 (in french)
Needs this also.
Basic implementation : a list of fields for which the data needs to be copied to the new child issue.
Extended implemenation : a mapping table - "from parent issue field to child issue field"
82 votesWalter supported this idea ·
And need this also. Currently we tell the users that the type of the first child issue needs to be changed, from then on he can create sibling issues and the type is copied. It works but UX drops.