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

Fetching fields meta does not work when issue type has been renamed

XMLWordPrintable

    • 6
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 November 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

      In a scenario where the Issue Type of Jira has been renamed (or the same name, but different case).
      The REST Query to get list of issue types : [ http://jira-server:9090/rest/api/2/issuetype ] returns the value of Issue Name that existed before the update.

      In our case, we renamed the Bug to BUG.
      The query for list of issue type in JIRA returns Bug.
      But using this return value to fetch list of fields meta [ http://jira-server:9090/rest/api/2/issue/createmeta?projectKeys=SP&issuetypeNames=Bug&expand=projects.issuetypes.fields ] from Jira, empty list is returned. Whereas the same second query but with value as BUG returns proper value.

      Thus, Jira expects/returns Issue Name differently at different instances.

              Unassigned Unassigned
              ae8830d605c0 Hiren Savalia
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: