Keypup allows you to connect your usual tools (GitHub, GitLab, JIRA, Trello...) for a smooth tracking of all pull requests and issues. But until now, users were able to connect one account per tool only.
There are some cases where a company has multiple JIRA sites, either for different clients or different projects. Well, we've made some enhancements for you to track projects across multiple JIRA instances.
If you are an agency, company or freelancer working on multiple client JIRA sites, this new feature is just for you.
Let's see how to consolidate them all on Keypup to have one nice organized view.
Connecting multiple JIRA sites
Head to Profile > Apps & Projects > Connected Apps. Here you can connect JIRA for the first time.
This will trigger the OAuth flow with Atlassian where you will be asked to choose a site to connect.
Unfortunately Atlassian does not allow users to select multiple sites at once, therefore we'll have to redo this connection process for each site. This is a one-off though. Once done, it's done!
Back onto Keypup, you will see your JIRA projects being imported. The protip above will invite you to connect additional JIRA sites. You can do so immediately.
Alternatively, you can head back to Profile > Apps & Projects > Connected Apps and click on the + (plus) button to connect additional JIRA sites.
Both methods will trigger the Atlassian OAuth flow again and allow you to select additional sites to connect.
After this authorization flow you will be redirected once again to the projects page. You can keep adding as many JIRA sites as you need then select which projects you wish to import on the projects page.
What about identities?
If you are the person who connected the JIRA sites, you do not need to do anything. Your JIRA identity is already authorized to access all the sites you connected.
If you have been invited to Keypup and your administrator has connected multiple JIRA sites, you will need to also authorize these additional JIRA sites on your JIRA identity if you wish to be able to comment on JIRA issues from Keypup.
It's easy to do so. After connecting your JIRA identity for the first time, you will see the following + (plus) button appearing in front of your JIRA identity.
Click on it and the OAuth flow will be triggered again. Choose the additional site you wish to authorize and click Accept.
That's it. You will now be able to remotely comment on issues belonging to this JIRA site.
What about JIRA custom fields in the data explorer?
JIRA custom fields are site-specific. Keypup therefore follows that approach by showing all custom fields and to which site they belong.
This approach creates duplication in the field list but ensures that each filter you create based on custom fields is site-specific, with no risk of returning unexpected results from other sites.
You can create thematic filters across sites using OR groups. For example let's say that your issue backlog status is called "To Do" on JIRA site 1 and "To Fix" on JIRA site 2.
You can create a custom report (or board column in the Team Board) regrouping all backlog items using a query like this:
No matter the naming conventions and workflow specificities in your JIRA sites, you can harmonize your overall workflow statuses in Keypup by regrouping definitions using JIRA custom fields and OR queries in your filters.
That's it for now. We hope we are contributing more to your daily work with this new feature. Each feature is a step closer to make Keypup the ultimate virtual assistant for developers. What do you think about JIRA multiple sites?
If you are not a Keypup member yet, sign up for free here.