-
Suggestion
-
Resolution: Unresolved
-
None
-
53
-
Hi everyone,
Thanks for providing your thoughts and votes on this suggestion. We know it's been a while since this suggestion was raised and we're sorry to have kept you without a clear answer.
Your feedback has really helped us better understand the challenges you face being unable to link Bitbucket Server projects with Jira instances. Despite our lack of communication, this problem is actually one of those areas we plan to improve. Right now we've decided to prioritise it on our roadmap.
Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we work on the solution.
Best,
Anton Genkin | Product Manager - Integrations
Original description:
Some of the reasons to provide this functionality:
- If two JIRA instances contain the same project key only the issue in the first instance that is found is displayed.
- Serial search through JIRA instances is not ideal.
- https://jira.atlassian.com/browse/STASH-4805
- is related to
-
BSERV-4805 Cannot follow link to JIRA issue if user does not have access to all linked JIRA instances
- Closed
-
BSERV-2471 Support integration with multiple JIRA servers
- Closed
- relates to
-
BSERV-10537 Warn or notify users when commit is linked to issue key present in multiple different Jira instances
- Gathering Interest
-
JRACLOUD-83584 Warning on new connections to a same product
- Gathering Interest
- causes
-
PS-58480 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...