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

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

          Form Name

            [JSWSERVER-945] Add a separate field to allow tracking sprint and release information independent of one another

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069398 ] New: JAC Suggestion Workflow 3 [ 3660086 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626554 ] New: JAC Suggestion Workflow [ 3069398 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327782 ] New: Confluence Workflow - Public Facing v4 [ 2626554 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044631 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327782 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032883 ] New: JIRA PM Feature Request Workflow v2 [ 2044631 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 739077 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032883 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: atlassian_status New: affects-server atlassian_status
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 540000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 302283 ] New: JIRA PM Feature Request Workflow v2 [ 739077 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Andrew made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 73459 ]
            Andrew Lui [Administrative Account] made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 64902 ] New: This issue links to "Page (Extranet)" [ 64902 ]

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

                Created:
                Updated:
                Resolved: