-
Suggestion
-
Resolution: Answered
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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
-
- Closed
[JRACLOUD-26885] Transition end-point can be "Self" as well as a specific state
| Workflow | Original: JAC Suggestion Workflow [ 3154672 ] | New: JAC Suggestion Workflow 3 [ 3636449 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2332528 ] | New: JAC Suggestion Workflow [ 3154672 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Component/s | New: Project and System Administration - Workflows and statuses [ 53194 ] | |
| Component/s | Original: Project Administration - Workflows [ 46562 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2097824 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2332528 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2062189 ] | New: JIRA Bug Workflow w Kanban v6 [ 2097824 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1865795 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2062189 ] |
| 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 Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-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 is related to |
| Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |
