Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-21868

Transitioning from a non-editable workflow status to another non-editable workflow status allows user to edit fields

XMLWordPrintable

    • 4.01
    • Severity 2 - Major
    • Hide
      Atlassian Update – 04 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 04 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      This is a bit of an interesting workflow case we discovered today. If a user creates a workflow with 2 steps that are not editable (via the jira.issue.editable step property) and transitions between the two steps then in theory none of the fields should be editable, since they can't be edited in the source step and destination step.

      If fields are added to the transition screen however they can happily be edited since the fields don't care about the source & destination workflow steps or if they are editable.

      The CommentAssignIssueAction should probably check if both the source and destination workflow steps are editable and if both aren't then not show any fields on the transition screen. Similarly the validateTransition method in the issue service should do the same check and throw an error.

      Note however that both the source & destination steps have to be not editable for this to be the case! If either the source or destination are editable, fields should still render and be editable (to allow users to assign when reopening/closing an issue for example).

      This probably only affects a very small number of users who happened to configure their workflows this way.

              Unassigned Unassigned
              andreask@atlassian.com Andreas Knecht (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: