github-for-jira
github-for-jira copied to clipboard
Feature request: support tagging?
Hey,
Just wondering if there is any intention to support tagging with that integration?
Would help organize tickets into releases (i.e. tag).
Thanks.
Hi @andreacab. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
I've flagged this with the 'to-triage' label so my team can discuss. We'll keep you posted on the status of this.
Hi @andreacab, do you mind providing more details on the use-case?
Hi @andreacab. As we haven't heard from you in a while, I'm going to go ahead and close this issue. If you would still like the team to look into this, please feel free to reopen and see the above message from @ccrolf.
Maybe I can add my use case.
Some context: Our Product Manager (PM) only has access to Jira and we use changesets to manage our releases on Github.
When we release something to production, we create a Github Release (which is also a git tag) with the links of all the PRs merged for that release. But to share this with my PM I have to manually create a corresponding Jira release and add all the tickets of the merged PRs.
This means we end up maintaining releases in 2 places, in Github and Jira and sometimes they go out of sync because we forget to create a Jira release. Another reason we use Jira Releases is that we have a Jira Automation setup that sends release notes to Slack/Emails on marking it as "Released".
What I would like is for this sync to happen automatically, creating a Github Release should automatically create a corresponding Jira Release and it should figure out the tickets from the PRs that were a part of it.
Thanks @rohit-gohri. I've reopened this issue and will discuss with our team.
Hello @rachellerathbone,
Where are you guys with this feature? In our team we miss it too and have the same use case as mentioned by @rohit-gohri
I'm also waiting for this feature. As our team manages both jira release feature and git tag, We need this feature as rohit-gohri commented.