Usage
Learn how to use Currents Jira Integration
Once enabled, you can create new or link an existing Jira issue directly from test execution details in Currents. You can also explore previously created or linked issues that are linked to the current test.
Browse Linked Jira Issues
- Open any test execution details in Currents 
- Look for the Jira icon (only visible when integration is enabled). If there existing (previously linked) Jira Issues related to the test, you will see a counter next to Jira icon. 


By clicking on the icon you can:
- Explore linked Jira Issues 
- Create a new Jira Issue 
- Link an additional existing Issue 
Create a New Jira Issue
To create a new issue:
- Select the Jira Project and Issue Type 
- Enter Issue Title and Description (optional) 
- Toggle Include Details to automatically add test context (error messages, stack traces, etc.) 
- Click Create Issue 
Example of a newly created issue:


Link an Existing Jira Issue
To link and comment on an existing issue:
- Select a Jira Project 
- Search for the issue by typing its title (results limited to 50 items) - Note: For more specific results, use more detailed search terms. 
- Enter your comment text 
- Toggle Include Details to add test context 
- Click Add Comment 
Example of commenting on an existing issue:


Browsing Linked Jira Issues
Open Jira dialog to list existing Jira Issues linked to the current test.
- Click on the Jira Issue ID to explore its details (opens a new tab) 
- Click 💬 to add a new comment to an existing issue 
- Click ⛓️💥 to unlink Jira Issue from the test 
- Click Add Jira Issue to create new or link an additional Jira Issue 

Notes
- The integration creates one-way links from Currents to Jira 
- Deleting or closing Jira Issue do not remove those issues in Currents - you will need to do that manually 
- Comments include a link back to the relevant test in Currents 
Limitations
Required Jira issue custom properties
Problem: Jira issues allows required custom properties when an issue is created depending on the issue type. This is currently not supported in our integration, as we can't send custom payload to the create issue endpoint.
Solution: Two options are available to overcome this issue. First,
- Don't enforce custom properties as required. 
- Use a different issue type that has no required custom properties. 
Last updated
Was this helpful?
