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...
Avigail Ehrenhaus
over 8 years ago
in Jira
0
Shipped
Guide users to reload configuration when missing field in mappings
When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
Madeleine Black
almost 2 years ago
in Jira
0
Shipped
Provide ability to map Created by user to Reporter field in the JIRA integration
When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...
Configure JIRA integration for multiple products/projects at once
We have a large organization with ~400 projects in JIRA, where 1 JIRA project = 1 agile team. We would like to sync all teams' epics with Aha, but the current UI only allows creating integrations 1 product at a time. Assuming 1 Aha product = 1 JIR...
Synchronize logged time and remaining estimates from Jira back to advanced estimates
Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...
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...
We are getting ready to share Aha with key stakeholders around the company, and we do not want to share the inside engineering chatter with the rest of the company. We have comments in JIRA that should not be broadly available. I would like to be ...
Cameron O'Rourke
over 8 years ago
in Jira
4
Shipped
Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use ...
Add a "Do I need a webhook" test on Jira integration screen
When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...
Madeleine Black
almost 2 years ago
in Jira
0
Shipped
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...