-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
feat(eco): Adds new RPC method for surfacing externally linked issue summaries #96699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
❌ 22 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the steps make sense to me, some terminology questions though for the PR descr.
- I assume context pane refer to the sidebar on the Jira side?
- Is the Jira parser an endpoint? What is that referring to? Is that a Jira side thing?
@@ -45,3 +46,25 @@ def upsert_issue_email_reply( | |||
# Call the task synchronously so that the outbox retry works | |||
# correctly should this fail. | |||
process_inbound_email(from_email, group_id, text) | |||
|
|||
def get_linked_issues( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could be better to specify this naming/function is specifically for integrations (?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah let me update that. Originally it didn't have integrations in the query, but turns out it was needed because external issue keys aren't unique.
0124e08
to
2044423
Compare
Backstory
We've wanted to enable Jira multi-region support for a while (#80381), but have been blocked on a couple of different fronts:
Jira Context Pane
This is the pane we're populating in Jira with requests to the
/issue/<external-issue-key/
URL in control:Atlassian Docs
Why this change?
This is the first step, of many, to enable Jira multi-region support.
This new RPC is meant to back a new multi-region version of the Jira Issue Context pane, which will now:
The current pane, as-is, is rather cluttered, and will only get worse once we allow multiple issues from multiple organizations in multiple regions to link to the same ticket. This is meant to back an abbreviated version of the existing preview pane with links to the corresponding issue links.
Checklist for Jira Multi-Region Support (subject to change):