-
Suggestion
-
Resolution: Answered
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
In order to allow users to edit only a subset of fields without transitioning to another state, it is common to create a transition which has the same starting and ending state. This transition's purpose is primarily to provide a screen with exactly the fields which this particular user should be allowed to modify at this point (e.g. the reporter of an issue should be allowed to change the summary and priority of an issue at any time, but not the assignee or fix version)
Without this feature, if the same functionality is desired at multiple states, individual transitions will have to be created. If there are any conditions, validations or post-functions those will have to be manually kept in synch.
With this feature, a single common transition could be re-used across multiple states.
- is related to
-
- Gathering Interest
- relates to
-
- Closed
[JRASERVER-26885] Transition end-point can be "Self" as well as a specific state
Doug Gray
added a comment - Roy,
Yes, clearly you can create a transition that loops the status (from the description: "it is common to create a transition which has the same starting and ending state"). This feature request is to allow a transition to be defined such that the end-point is not a specific state, but rather a generic Self. This would allow the same transition to be re-used across multiple states as opposed to having to create a separate transition for each state to which we want to apply the transition.
If this capability currently exists, then please describe how to accomplish or re-open so that it be can considered as a potential future feature request.
Doug Gray
added a comment - Roy,
Yes, clearly you can create a transition that loops the status (from the description: "it is common to create a transition which has the same starting and ending state"). This feature request is to allow a transition to be defined such that the end-point is not a specific state, but rather a generic Self . This would allow the same transition to be re-used across multiple states as opposed to having to create a separate transition for each state to which we want to apply the transition.
If this capability currently exists, then please describe how to accomplish or re-open so that it be can considered as a potential future feature request. Hi Doug,
Thanks for raising this.
I'm pretty sure you can already create a transition that loops the status. We also now have in-line edit and users can also customise their own edit screen.
Cheers,
Roy Krishna
JIRA Product Management
I don't think the underlying OSworkflow supports that, though good docs are not easily available. I would use this idea for a transition to clear the resolution of an issue from any status.
However if you just want field level security you could use the Behaviors plugin you can restrict who can change fields, and when.