We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Jira Software Data CenterProject Type: software

Jira Software Data Center

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

Add a separate field to allow tracking sprint and release information independent of one another

XMLWordPrintable

    • Hide
      Atlassian Status as at July 18, 2012

      Sprints are now implemented using a separate custom field in GreenHopper 5.10 and later on the Rapid Board.

      The Rapid Board use of this field frees up fixVersion field for normal use.

      More information on the road ahead for GreenHopper can be found in The Future of GreenHopper

      Regards,
      Shaun Clowes

      Show
      Atlassian Status as at July 18, 2012 Sprints are now implemented using a separate custom field in GreenHopper 5.10 and later on the Rapid Board. The Rapid Board use of this field frees up fixVersion field for normal use. More information on the road ahead for GreenHopper can be found in The Future of GreenHopper Regards, Shaun Clowes
    • 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.

      At present, we're using Versions for our Software Versions (e.g. 0.9.0) and Sprints (e.g. Sprint 1) and then use the hierarchy to set Parents to Children e.g. Version 0.9.0 includes Sprint 1, Sprint 2 and Sprint 3. Is it possible to have a seperate 'version' just for Sprints? Then use the drop down list in the Planning Board (right hand column above 'versioning boxes') to display Sprints alongside Versions, Components etc.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-945

            Add a separate field to allow tracking sprint and release information independent of one another

            XMLWordPrintable

              • Hide
                Atlassian Status as at July 18, 2012

                Sprints are now implemented using a separate custom field in GreenHopper 5.10 and later on the Rapid Board.

                The Rapid Board use of this field frees up fixVersion field for normal use.

                More information on the road ahead for GreenHopper can be found in The Future of GreenHopper

                Regards,
                Shaun Clowes

                Show
                Atlassian Status as at July 18, 2012 Sprints are now implemented using a separate custom field in GreenHopper 5.10 and later on the Rapid Board. The Rapid Board use of this field frees up fixVersion field for normal use. More information on the road ahead for GreenHopper can be found in The Future of GreenHopper Regards, Shaun Clowes
              • 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.

                At present, we're using Versions for our Software Versions (e.g. 0.9.0) and Sprints (e.g. Sprint 1) and then use the hierarchy to set Parents to Children e.g. Version 0.9.0 includes Sprint 1, Sprint 2 and Sprint 3. Is it possible to have a seperate 'version' just for Sprints? Then use the drop down list in the Planning Board (right hand column above 'versioning boxes') to display Sprints alongside Versions, Components etc.

                        Unassigned Unassigned
                        1bb16a2139a4 Toby Mildon
                        Votes:
                        163 Vote for this issue
                        Watchers:
                        128 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              1bb16a2139a4 Toby Mildon
                              Votes:
                              163 Vote for this issue
                              Watchers:
                              128 Start watching this issue

                                Created:
                                Updated:
                                Resolved: