Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-87679

Milestones for Advanced Roadmap based on custom date Jira field

    • 2
    • 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.

      As a Project Manager, I created some Epic tickets contains custom date Jira field like :

      • Date Design
      • Date Developement
      • Date UAT
      • Date Production

      I would like see these dates like a milestone on Advanced Roadmap

       

            [JRACLOUD-87679] Milestones for Advanced Roadmap based on custom date Jira field

            Team - is there an update on this feature?

            Anika Sharma added a comment - Team - is there an update on this feature?

            MBharucha added a comment -

            I also want to be able to represent milestones within a Jira Plan (Advanced Roadmaps).

            My use case is a little different than what's in the ticket description:

            For each Production Release, we have key milestone dates like Feature Freeze, Code Freeze, UAT Start, etc.  It would be convenient and appropriate to capture these planning dates on the Release itself, and then have those release milestones shown in our Jira plan.  I've seen some folks using the workaround of creating a separate "release" per milestone, but I think that could get really confusing for our various scrum teams in 5+ time zones, and we'd probably have to set up extra field validation rules to prohibit users from assigning tickets to those releases-that-are-not-actually-releases.

            MBharucha added a comment - I also want to be able to represent milestones within a Jira Plan (Advanced Roadmaps). My use case is a little different than what's in the ticket description: For each Production Release, we have key milestone dates like Feature Freeze, Code Freeze, UAT Start, etc.  It would be convenient and appropriate to capture these planning dates on the Release itself, and then have those release milestones shown in our Jira plan.  I've seen some folks using the workaround of creating a separate "release" per milestone, but I think that could get really confusing for our various scrum teams in 5+ time zones, and we'd probably have to set up extra field validation rules to prohibit users from assigning tickets to those releases-that-are-not-actually-releases.

            please could you share an update on this

            Parimala Narayanan added a comment - please could you share an update on this

            Ae you able to provide an update on this feature request please?

            andy rowles added a comment - Ae you able to provide an update on this feature request please?

              Unassigned Unassigned
              10e07900466e Thibaut FAURE
              Votes:
              32 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: