Rachelle Rathbone

This feature is now fully rolled out 🎉 so closing this issue.

I haven't been able to reproduce this. Looks like this may have already been resolved when we updated how we handled deployments. Going to go ahead and close.

Hey @rmani07. Unfortunately not. At this point if you install the app, connect an org/s, and give permission to repos, any issue key references in in pull requests, commits etc...

Hey @stepanruzickamooza. Are you still having an issue with this? If so, please send your Jira instance site name through and I can take a look at our logs.

Hey @beliaev-maksim. Unfortunately, this is not something that is currently supported in our integration. That said, it is becoming a heavily requested feature which helps push it to the top...

Hey @xukio. If you can send me your Jira site url I can take a look at our logs for you.

Hey all. Unfortunately, this regression is the result of a upstream team changing the way they store data. A team mate of mine is working on a doc to outline...

Our SUPPORT docs have been updated with more info and a temporary workaround https://github.com/atlassian/github-for-jira/blob/main/SUPPORT.md#unmapped-users Unfortunately, this is not the most ideal solution but it is the best we can do...

@blackheart-atlassian if you can fix the failed push / build check we'll be able to approve this and get it merged in.

Hey @gorohovart. Thanks for attempting to do this. Unfortunately, it's not so simple. Jira doesn't currently doesn't recognise the PR status of 'DRAFT' and there are a number of services...