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

Statuses in a visual workflow show 'Step Name (id)' values as opposed to 'Linked Status' values.

    XMLWordPrintable

Details

    • 1
    • Severity 2 - Major
    • Hide

      Atlassian Update – 04 July 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 – 04 July 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

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Statuses in a visual workflow show Step Name (id) values as opposed to Linked Status values.

      Since the Step Name (id) value is really only shown in the Steps Editor (and nowhere else throughout the JIRA UI), visual workflows should be reflecting Linked Status values instead.

      By implementing this fix, then whenever the JIRA (project) administrator edits the name of a status in the VWD's status editor, the name change should be reflected in the visual workflow (and for ordinary JIRA users, the workflow view of JIRA issues which use that workflow).

      Bear in mind that changing a status' name in the VMD affects all other workflows that use the same status. This is considered expected behaviour. To create a status that's workflow-specific, the JIRA (project) administrator would need to create a completely new status (i.e. Linked Status) to use in the workflow.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-25429 Statuses in a visual workflow show 'Step Name (id)' values as opposed to 'Linked Status' values.

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22637 Issue status modifications do not reflect in workflow steps and issue navigator search terms

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRASERVER-17228 Why not use Status Id as Step id in OSWorkflow?

          • Closed
          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-27913 The view issue page's visual workflow shows 'Step Name (id)' values for 'Statuses' as opposed to 'Status' values themselves.

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              ggaskell Giles Gaskell [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: