-
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
| Workflow | Original: JAC Suggestion Workflow [ 3048810 ] | New: JAC Suggestion Workflow 3 [ 3691956 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Link | New: This issue is related to JSWSERVER-19879 [ JSWSERVER-19879 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2608961 ] | New: JAC Suggestion Workflow [ 3048810 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2561774 ] | New: Confluence Workflow - Public Facing v4 [ 2608961 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358539 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2561774 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2125943 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358539 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088459 ] | New: JIRA Bug Workflow w Kanban v6 [ 2125943 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 885433 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088459 ] |
| Description |
Original:
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. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-26885]. {panel} 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. |
| Link |
New:
This issue relates to |
