Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15687

Software project release documentation update in Confluence

XMLWordPrintable

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

      Problem Definition

      Developers have to maintain a separate documentation in Confluence for versions and release information intended for non-technical stake holders. On a JIRA Software Project with frequent releases, this introduces a lot of overhead for developers.

      Suggested Solution

      Automate some documentation updates when a version is released in the JIRA Software Project.

      When the "Release" button is clicked for a version in the JIRA Software Project :

      • Update a "Released Versions Overview" page in the linked Confluence Space.
      • Create a page for the version using the Change Log Blueprint.

      Why this is important

      Versions and release information are relevant to non-technical stakeholders who doesn't necessarily need to be granted access to JIRA Software. Having the feature will reduce overhead of updating documents manually in Confluence every time a release is done in JIRA Software.

              Unassigned Unassigned
              rmacalinao Ramon M (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: