Jira
Sort by:
Recent
Status:
Shipped
Showing 87
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
4
VOTE
Mapping of Initiatives to other ticket types in Jira
Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...
1
Shipped
7
VOTE
allow clicking on JIRA ticket-id in feature_grids view
right now if i add the column "jira key" (or even jira-link), and i want to see the ticket in jira, i have to copy it from the UI, and go to JIRA to paste it (or my browser's URL) to see the ticket in JIRA.this can be solved by making the col to b...
0
Shipped
1
VOTE
Add setting to the Aha! Integration Configuration to just update one way for JIRA to Aha
Why I hear you ask? 2 main reasons: -
JIRA always wins for companies that use JIRA as the master
To get round the issue of Aha! breaking the formatting when JIRA uses a plugin (Jeditor)
A one way update fixes all issues.
Setting as a checkbox de...
0
Shipped
3
VOTE
Ability to send static attributes to JIRA
Engineering has made many attributes in JIRA mandatory, which means I need to create custom fields. They would be OK with a static value that would identify it as coming from Aha!, as they want to make sure they are filled correctly manually but t...
3
Shipped
7
VOTE
Add integration support for the new "Users field" custom field type with JIRA custom field type "user picker"
We just launched the new custom field type "Users field". It would be powerful to be able to integrate this with JIRA and specifically, integrate it with the JIRA custom field type "User Picker".
2
Shipped
20
VOTE
JIRA Integration: Option to disable Assignee Integration
If you have an environment where the engineers are not setup in Aha!, what ends up happening for when you have Features/Requirements linked to JIRA Issues is when assignments are made in JIRA, the assignee information that is synced back to Aha! d...
2
Shipped
29
VOTE
29
VOTE
Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects
The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...
3
Shipped
24
VOTE
Turn off 2-way synch for specific custom fields sent to Jira
Up until recently, custom field data was sent one-way Aha to Jira.
For certain fields, we prefer the data sent one-way. We want to be able to send information such as business goals so that people using Jira can understand more about what's trying...
0
Shipped