• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Plans - Timeline
    • None
    • 1
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Right now Portfolio is very software-centric. It would be desirable for an admin to be able to rename several built-in fields. For example, it should be possible to rename Releases to Milestones.
      That would make Portfolio more generic. Examples of milestones in our context: PDR, CDR, TRR, etc (http://en.wikipedia.org/wiki/Design_review_%28U.S._government%29)

            [JRACLOUD-88096] Rename Release as Milestone

            We are using versions/releases for releases and milestones. It would be good to be able to check a box on the release to distinguish it from milestones. It is useful to have both releases and milestones in the same place, as they are often very closely related.

            Julia Murphy added a comment - We are using versions/releases for releases and milestones. It would be good to be able to check a box on the release to distinguish it from milestones. It is useful to have both releases and milestones in the same place, as they are often very closely related.

            I don't see why there can't be both.

             

            And yet...here we are: 

            JSWCLOUD-20254 Milestones - Create and track feature requests for Atlassian products.

            JSWCLOUD-17652 Milestones for Basic Roadmaps - Create and track feature requests for Atlassian products.

            Deleted Account (Inactive) added a comment - I don't see why there can't be both.   And yet...here we are:  JSWCLOUD-20254 Milestones - Create and track feature requests for Atlassian products. JSWCLOUD-17652 Milestones for Basic Roadmaps - Create and track feature requests for Atlassian products.

            Versions and releases are confusing for most of my customers; I tell them they just need to understand that Version and Releases labels are used interchangeably within JIRA. This is non-desirable. Either allow us to rename the constructs or keep the naming 'Versions' as it exists within JIRA proper.

            Steve Behnke [DiscoverEquip.com] added a comment - Versions and releases are confusing for most of my customers; I tell them they just need to understand that Version and Releases labels are used interchangeably within JIRA. This is non-desirable. Either allow us to rename the constructs or keep the naming 'Versions' as it exists within JIRA proper.

            In our company we use release and milestone as two separate entities. Release is used for software releases and milestone for high level planning. A milestone may include multiple releases. Showing milestone on the Gantt chart would be cool feature as well.

            Vahid Babaloo added a comment - In our company we use release and milestone as two separate entities. Release is used for software releases and milestone for high level planning. A milestone may include multiple releases. Showing milestone on the Gantt chart would be cool feature as well.

            Agreed, we just used the release for a grant-funded project and use the Project Phases as releases for one project and the high level project objectives as releases for the other project, which is confusing our non-techy users

            Jessica Malenfant added a comment - Agreed, we just used the release for a grant-funded project and use the Project Phases as releases for one project and the high level project objectives as releases for the other project, which is confusing our non-techy users

              Unassigned Unassigned
              85925909ef7a Patrick Dubois
              Votes:
              26 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: