Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1316

Business Value field editable

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      The Business Value of an Initiative or Epic is the most important parameter for prioritization.
      However JIRA Portfolio does not have a field or column to indicate the Business Value.

      Oddly enough the CSV export includes a field or column "BusinessValue", just next to "Estimate_Total" and "Estimate_Original" ...

      Please make the Business Value field or column visible and editable in JIRA Portfolio.

          Form Name

            [JPOSERVER-1316] Business Value field editable

            Albert Kavelar added a comment -

            Hello wiebe.bijlsma1800912446,

            thanks for your reply, I will resolve this ticket then. Regarding the Business Value field in the CSV export - there is, in fact, a dark feature you can enable for Portfolio that allows you to show a Business Value column where you can enter a numeric value. This column, however, is in no way connected to the business value in JIRA - it does neither pull in JIRA's value nor does it allow you to push this value from Portfolio to JIRA, so it provides a somewhat limited functionality.

            In case you want to still give this a try, if this still provides value to your use case, let me know, I can tell you how to enable this in your instance.

            Please make sure to vote for the two linked suggestions and have a look at Atlassian's policy on implementing new features.
            Best regards,
            Albert

            Albert Kavelar added a comment - Hello wiebe.bijlsma1800912446 , thanks for your reply, I will resolve this ticket then. Regarding the Business Value field in the CSV export - there is, in fact, a dark feature you can enable for Portfolio that allows you to show a Business Value column where you can enter a numeric value. This column, however, is in no way connected to the business value in JIRA - it does neither pull in JIRA's value nor does it allow you to push this value from Portfolio to JIRA, so it provides a somewhat limited functionality. In case you want to still give this a try, if this still provides value to your use case, let me know, I can tell you how to enable this in your instance. Please make sure to vote for the two linked suggestions and have a look at Atlassian's policy on implementing new features . Best regards, Albert

            Wiebe Bijlsma added a comment -

            Albert,

            Indeed my suggestion is very similar to JPO-136 (not so much JPO-132). Therefor it's fine to close this one.

            I will have a look at the suggestion to use custom fields.

            But I still wonder what the intended use is of the field already available in the JIRA Portfolio CSV export, namely "BusinessValue". This is only visible in the CSV export, not in JIRA Portfolio itself.

            Kind regards,

            Wiebe Bijlsma

            Wiebe Bijlsma added a comment - Albert, Indeed my suggestion is very similar to JPO-136 (not so much JPO-132 ). Therefor it's fine to close this one. I will have a look at the suggestion to use custom fields. But I still wonder what the intended use is of the field already available in the JIRA Portfolio CSV export, namely "BusinessValue". This is only visible in the CSV export, not in JIRA Portfolio itself. Kind regards, Wiebe Bijlsma

            Albert Kavelar added a comment -

            Hello wiebe.bijlsma1800912446,

            thanks for sharing this suggestion with us. There already are two suggestions - JPO-136, JPO-132 - for making use of the Business Value. As of now, we don't allow syncing JIRA's Business Value with Portfolio, please understand that we cannot provide a timeline for when this will be introduced, please have a look at Atlassian's policy on implementing new features.

            There also is a more general suggestion for making custom fields from JIRA accessible via Portfolio, this actually sounds like what you are looking for. So if you are fine with it, I'd like to close this suggestion as duplicate. Please let me know if that's okay for you or if you prefer to keep this particular suggestion open.

            Best regards,
            Albert Kavelar | Portfolio for JIRA Development

            Albert Kavelar added a comment - Hello wiebe.bijlsma1800912446 , thanks for sharing this suggestion with us. There already are two suggestions - JPO-136 , JPO-132 - for making use of the Business Value . As of now, we don't allow syncing JIRA's Business Value with Portfolio, please understand that we cannot provide a timeline for when this will be introduced, please have a look at Atlassian's policy on implementing new features . There also is a more general suggestion for making custom fields from JIRA accessible via Portfolio, this actually sounds like what you are looking for. So if you are fine with it, I'd like to close this suggestion as duplicate. Please let me know if that's okay for you or if you prefer to keep this particular suggestion open. Best regards, Albert Kavelar | Portfolio for JIRA Development

              Unassigned Unassigned
              ac611d56a1f6 Wiebe Bijlsma
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: