Jira
Sort by:
Trending
Status:
Showing 265
2
VOTE
Allow integration of Custom Fields to any Jira Field of a supported field type
We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field.
We would like to push this custom field valu...
0
Already exists
1
VOTE
1
VOTE
Allow 2-way integration to Jira FixVersion/s field from text field
Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...
0
Future consideration
1
VOTE
2
VOTE
JIRA and Aha synchronized numbering
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
0
Unlikely to implement
1
VOTE
Add "Select all" option to Integration Updates page
As a user, I want the ability to "select all" updates on the Integration Updates page, so that I do not have to select each change to send manually. When the user has set up integrations on a workspace, if there are issues with some of the integra...
3
Already exists
1
VOTE
Add Closing Comment for Jira Integration
Our Jira environment has a requirement to enter a comment when "closing" a ticket. Aha does not have a place for this so if Aha! users close a feature in Aha, they will have to login to Jira and close it there as well. The request is to allow a "c...
0
Future consideration
2
VOTE
Keep unsupported 3rd party Jira tag as it is upon syncing
In Jira, it is possible to render Gherkin by using 3rd party plugin.
After modify the description field in Aha! and synced with Jira, the format is ruined by Aha!.
Original Description on Jira:{code:gherkin} Scenario: The empty state text shows...
0
Will not implement
2
VOTE
Need an option to sync Jira fixVersion "Name" instead of "ID"
Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
0
Already exists
1
VOTE
© 2024 Aha! Labs Inc.•All rights reserved