Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-5204

readme.md and changelog.md were auto generated by Confluence and JIRA

XMLWordPrintable

    • We collect Bitbucket 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.

      It’s important to have documentation, issues, and code in the proper places. As such, code belongs in stash, issues in jira, documentation in confluence. However, there are a couple of items that should be kept with the code- a change log and a readme file. It would be nice if these non-code files could be automatically generated from the places where the data actually resides.

            [BSERV-5204] readme.md and changelog.md were auto generated by Confluence and JIRA

            Rijnhard Hessel added a comment - - edited

            rbarnes used the wrong user.

            and actually funny enough I am busy setting that up as we speak.

            Rijnhard Hessel added a comment - - edited rbarnes used the wrong user. and actually funny enough I am busy setting that up as we speak.

            Roger Barnes (Inactive) added a comment -

            licenses32, the release hub might suit your use case. It shows issues assigned to each version, and also highlights where the issue status is not reflected by corresponding state in the code (eg a merged pull request)

            Roger Barnes (Inactive) added a comment - licenses32 , the release hub might suit your use case. It shows issues assigned to each version, and also highlights where the issue status is not reflected by corresponding state in the code (eg a merged pull request)

            Roger Barnes (Inactive) added a comment -

            For now I'm going to go ahead and close this, but would consider reopening and directing to a more appropriate product backlog given more input.

            Roger Barnes (Inactive) added a comment - For now I'm going to go ahead and close this, but would consider reopening and directing to a more appropriate product backlog given more input.

            Roger Barnes (Inactive) added a comment - - edited

            This is an interesting request. Fundamentally, a plugin in any one of JIRA, Confluence, Stash or Bamboo could generate or update a readme and/or changelog. Another build tool or external process could do this too.

            The most important factor I think that needs to be taken into account is the timing of updates, and to me, build or release time makes the most sense, which suggests that JIRA or Bamboo (which have release/deploy stages) would be ideal candidates for triggering file generation. Arguably, Stash is just the repository host for the result.

            I'm interested in responses to this idea, ideally with real-world workflows to support/refute it.

            Roger Barnes (Inactive) added a comment - - edited This is an interesting request. Fundamentally, a plugin in any one of JIRA, Confluence, Stash or Bamboo could generate or update a readme and/or changelog. Another build tool or external process could do this too. The most important factor I think that needs to be taken into account is the timing of updates, and to me, build or release time makes the most sense, which suggests that JIRA or Bamboo (which have release/deploy stages) would be ideal candidates for triggering file generation. Arguably, Stash is just the repository host for the result. I'm interested in responses to this idea, ideally with real-world workflows to support/refute it.

              Unassigned Unassigned
              kgrier kitkat (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: