The GLIDR & Jira Integration lets you seamlessly move ideas from roadmap to delivery, without losing context.
GLIDR to Jira
- When you push an Idea from GLIDR, it creates a new Issue in Jira. These two pieces of data are now linked across the two applications, which you can see because their connected cards are visible within one another.
- If you change the title/description of GLIDR card in GLIDR, those changes show up in the embedded GLIDR card in Jira. They do *NOT* change the title/description of the Jira card in Jira.
- Once the cards have been connected, Evidence that you connect to your GLIDR Idea will show up in Jira below the GLIDR widget. This lets your team members who use Jira to still understand the Evidence behind a feature.
- If you are a team member who has access to GLIDR but not Jira, you can see the data from the Integration, but if you try and click to view the Jira Issue, you will be prompted to log in and will be unable to view it.
Jira to GLIDR
- When you push an Issue from Jira, it creates a new Idea in GLIDR. These two pieces of data are now linked across the two applications, which you can see because their connected cards are visible within one another.
- If you change the title/description of Jira card in Jira, those changes show up in the embedded Jira card in GLIDR. They do *NOT* change the title/description of the GLIDR card in GLIDR.
- Once the cards have been connected, if you pushed an Epic, Stories that you connect to your Jira Issue will show up in GLIDR below the Jira widget. This lets your team members who use GLIDR to keep tabs of the Jira development process as the stories are completed.
- If you are a team member who has access to Jira but not GLIDR, you can see the data from the Integration, but if you try and click to view the GLIDR Idea, you will be prompted to log in and will be unable to view it.
What can't the integration do?
When we began research on the GLIDR & Jira Integration, we started with the simplest connection that would give the greatest value. After talking to many users, we decided on the structure and behavior of our current integration. That said, there are some more complex features that our users may want in the future. If you want to see any of the following features, shoot us a line and tell us why!
Existing issue links
Right now, you can push a GLIDR Idea to Jira, or push a Jira Issue to GLIDR, but there's no way to link two existing cards to one another. If you want to connect an existing GLIDR Idea and an existing Jira Issue, our integration doesn't allow for this.
One GLIDR Idea can be connected to one Jira Issue at any given time. If you want to connect one GLIDR Idea to multiple Jira Issues, or one Jira Issue to multiple GLIDR Ideas, this is not yet possible.
Viewing Jira Status on Product Canvas
In the GLIDR Product Canvas, both on the List View & the Kanban View, you can't yet see the Jira status of each connected Idea card. We're working on changing this, but for now, you can click through to open the Product Idea card and see its status, or go to Jira and see the status there.
Overwriting Updated Data
We did not yet want We don't mirror the statuses between GLIDR & Jira or overwrite them because most teams will use the two apps for different processes.
If you don't have sufficient permissions in your Jira instance, there are two quick fixes:
- Ask your Jira Site Administrator to upgrade your Jira permissions.
- Invite a Site Administrator from your Jira instance to your GLIDR organization, and ask them to implement the integration with their permission level. Once this is completed, you can disable their GLIDR account and continue using the integration.