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

When a transition has a screen that contains the issue type, JIRA updates the issue type to null if it's not set on the transition

    XMLWordPrintable

Details

    • 4.02
    • Severity 3 - Minor
    • 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

    Description

      See this issue: https://studio.atlassian.com/browse/JST-3918

      In this case, the customer was using the default screen for the transition, which included the ability to update the issue type. We were progressing this transition in response to a commit message from SVN, and were updating none of the fields, however, JIRA seems to be ignoring the fact that no issue type was set on the transition request, and updates the issue type of the issue to be null. This later results in a NullPointerException when permissions are checked for another field.

      This may be a problem for other fields, not sure. It seems here that the assumption is that because issue type is a select list, that it will always have a value. That's true when the transition is executed from the web interface, but its not true in any other workflow transition scenario. It also seems that the issue type field might not be being correctly validated before being set. What should happen is that it should be seen to be null in the transition request, and so not updated.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jroper James Roper [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: