|
Part of the bigger picture (
Tim,
Would most of this ticket be covered by JRA-4913? We appreciate your feedback. Please note however, that we have thousands of improvement and new feature requests. While we would like to do most of them, we, unfortunately, will never get the required resources to do so. Aggregating information helps us to better schedule issues that fit with the direction of the product and bring the most benefit to our users as described here: Therefore, if JRA-4913 does cover what this tickets discusses, could we close this as a duplicate? Please note that providing security over each issue field is covered by Also, please note, our aim for JIRA is to ensure that it works out of the box. It is very difficult to make everything conditional and configurable and still enforce consistency and data intergrity. JIRA is not mean to be a toolkit where one needs to invest 100s of hours of development work to get things just to run. Due to this, some things are not possible to get to work exactly how you need them oy of the box. Often, it is possible, and worthwhile to customise JIRA to do them. However, customisation will incur addition cost when upgrading. Whether this is worth it, depends on how important the requitement is. Please let us know if JRA-4913 or JRA-9802 address this request. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I know a lot of these tickets have been requested as one-offs, but this is just attempting to capture several requests and link it to a larger issue at hand.
Thanks