Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-24964

Broken "Fix Version" field in JIRA Portfolio - Portfolio operations on Releases overrides "fix version" designed to be a list , not a single value field.

XMLWordPrintable

    • 4
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      JIRa Portfolio brokes functionality of existing "Fix Version" field.

      In JIRA Software "Fix version" is a list of Versions.  They might be not only releases, but e.g build numbers , etc

      In JIRa Portfolio you limited it only to one value.

      Why ? Why it can't be a list with append possibility ?

          Form Name

            [JSWSERVER-24964] Broken "Fix Version" field in JIRA Portfolio - Portfolio operations on Releases overrides "fix version" designed to be a list , not a single value field.

            Blaudek-Premm, Joachim added a comment -

            This field is quite essential for planning purposes .... how comes that it takes ages to fix it.

            Blaudek-Premm, Joachim added a comment - This field is quite essential for planning purposes .... how comes that it takes ages to fix it.

            Hannes Medwed added a comment -

            Why the same problem  is a BUG in the cloud version (which is the right definition and has already been fixed) and a suggestion in the data center version.

            Hannes Medwed added a comment - Why the same problem  is a BUG in the cloud version (which is the right definition and has already been fixed) and a suggestion in the data center version.

            Xiaoqiao She added a comment -

            Vote for this to be fixed asap. 
            Today I noticed, it seems to show the entire list when I scroll up and down, but when the rendering finalized, it only shows one instead of the entire list. So hopefully it's not a hard fix.

            Xiaoqiao She added a comment - Vote for this to be fixed asap.  Today I noticed, it seems to show the entire list when I scroll up and down, but when the rendering finalized, it only shows one instead of the entire list. So hopefully it's not a hard fix.

            Aakrity Tibrewal added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            PM added a comment -

            I agree, this is really a bug, unfortunately not the only on in portfolio. Should be fixed right away!

            PM added a comment - I agree, this is really a bug, unfortunately not the only on in portfolio. Should be fixed right away!

            Manoj Gupta added a comment -

            Request the product manager to respond on this thread about ETA.  OR publish all such items you have diverted from original Jira configuration so that we don't waste our time in Portfolio migration. 

            Manoj Gupta added a comment - Request the product manager to respond on this thread about ETA.  OR publish all such items you have diverted from original Jira configuration so that we don't waste our time in Portfolio migration. 

            Manoj Gupta added a comment -

            Looks like Atlassian is not looking into these issues. this is a regression and should be fixed ASAP. you can't original system when you create another system that is integrated with the original system. isn't this straight forward fix? 

            Manoj Gupta added a comment - Looks like Atlassian is not looking into these issues. this is a regression and should be fixed ASAP. you can't original system when you create another system that is integrated with the original system. isn't this straight forward fix? 

            Joseph Chung Yin added a comment -

            We need to have this issue fixed as we are ready to upgrade to Jira DC Application version to 9.x.  This is a critical impact to our company's usage of AR for Jira.  It seems a duplicate case was created on our latest Support Case, but it was closed out by Atlassian - https://jira.atlassian.com/browse/JPOSERVER-4393.

            Best, Joseph

            Joseph Chung Yin added a comment - We need to have this issue fixed as we are ready to upgrade to Jira DC Application version to 9.x.  This is a critical impact to our company's usage of AR for Jira.  It seems a duplicate case was created on our latest Support Case, but it was closed out by Atlassian - https://jira.atlassian.com/browse/JPOSERVER-4393 . Best, Joseph

            Scott Cling added a comment -

            We also use multiple fix version/s in an issue and hence can't fully utilize Portfolio for JIRA, and also need to warn users that if they change release in Portfolio it will clear their other fix version/s that are selected and only keep the one chosen.

            This is definitely a shortcoming in Portfolio that causes much frustration.

            Scott Cling added a comment - We also use multiple fix version/s in an issue and hence can't fully utilize Portfolio for JIRA, and also need to warn users that if they change release in Portfolio it will clear their other fix version/s that are selected and only keep the one chosen. This is definitely a shortcoming in Portfolio that causes much frustration.

            Matt Wakeman added a comment -

            My company has a platform release and a product release. So almost every ticket has two versions / releases. 

            Matt Wakeman added a comment - My company has a platform release and a product release. So almost every ticket has two versions / releases. 

              Unassigned Unassigned
              joanna.maciag664753585 joanna.maciag664753585
              Votes:
              60 Vote for this issue
              Watchers:
              43 Start watching this issue

                Created:
                Updated: