Jira
Sort by:
Status:
Shipped
Showing 101
66
VOTE
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The int...
13
Shipped
7
VOTE
75
VOTE
Ability to map standard fields in Aha to custom fields in JIRA
It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example... - Assigned User to Product Owner - Aha Score to Business Value These are fields that we use in JIRA that we are having to manually type in aga...
10
Shipped
44
VOTE
Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" f...
12
Shipped
47
VOTE
Support for "Select list (cascading)" field type in JIRA
JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...
10
Shipped
47
VOTE
Map Aha Initiative to JIRA Portfolio Initiative
JIRA Portfolio allows for the notion of Initiatives. Portfolio is good for provide views for about 3 months (short-term), beyond that we have found it to struggle. It will be good to sync initiatives so it is possible for engineering to see what i...
11
Shipped
6
VOTE
Update Jira integration to use "Parent" instead of "Parent Link"
Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...
2
Shipped
13
VOTE
Improve visibility of integrations update modal
When users set up an integration and select "auto import records", they are not immediately aware that some records will not just automatically import into Aha! (i.e. those that don't have a parent record that is sync'd). These users are not able ...
0
Shipped
41
VOTE
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
7
Shipped
50
VOTE
Re-enable conversion of Features to Requirements when JIRA integration is active
In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
4
Shipped
© 2024 Aha! Labs Inc.•All rights reserved