Guy Fraser
My feedback
1 result found
-
86 votes
An error occurred while saving the comment An error occurred while saving the comment I'd like to extend this to optionally restrict what project the child issues can be in.
For example, issue type A in project FOO can only contain children of issue type B in project BAR.
The ability to use a wildcard for project / issue type, or a list of projects / issue types (or any mix of those scenarios) would be utterly awesome!
The reason for this is that we're using JIRA to basically manage our entire business. So, for example, we have a CRM project that lists customers, then a SALES project where we manage sales, LEGAL project for contracts, SLA/SUP projects for support, WORK projects for bespoke projects and so on.
We need to ensure, for example, that a SALES issue can't contain a CRM issue (because that would be sort of backwards in our desired hierarchy). So we'd want to say that CRM tickets can only have child tickets in the SALES project, and then SALES tickets can only have children in the LEGAL/SLA/WORK projects and so on.
In addition, we'd want to have certain types of SALES tickets only able to have children in specific projects and so on.
If permissions could also be wired in to this, so that specific user groups can only alter certain parts of the structure, I would cream my pants. That is all. :)