Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-50214

Show date range of JIRA versions

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • Confluence 5.3.4
      JIRA 6.1.4
    • We collect Confluence 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.

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

      In evaluating Team Calendars for our confluence instance I was very excited to see the option to import JIRA versions into the calendar. I even found a reference to this feature in another improvement https://jira.atlassian.com/browse/TEAMCAL-417 however, when I tied it out it did not work for me.

      What I want to do is using the "Start Date" and "Release Date" in jira for versions have that show up as a range bar in Team Calendars. Today only the Release Date shows up.

      I was told that this can be done via Agile which I tested and found it could do this. In addition to that I found that creating a custom issue type can do the same. However, I pefer and I think it is beneficial to users if there was only one place in JIRA to update a versions dates. In both the Agile and the issue type workaround a user would have to update the dates in more then one location. If this feature were implemented not only would users not "have to" buy Agile but it can be administered in one location in JIRA.

      It seem fairly straight forward that the fields are in JIRA already and the functionality of Team Calendars is there but the option to put these together is lacking.

              Unassigned Unassigned
              bf62f5f9-6993-48a7-8a99-5966f2eb55bb Deleted Account (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: