When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest
over 9 years ago
in Jira
8
Unlikely to implement
We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest
over 9 years ago
in Jira
5
Unlikely to implement
We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest
over 9 years ago
in Jira
9
Unlikely to implement
Convert story to epic in Jira when promoting requirement to feature
In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest
over 9 years ago
in Jira
2
Unlikely to implement
At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest
almost 10 years ago
in Jira
0
Already exists
Have users in Jira and Aha matched for comments, updates etc
I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there.
Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
Filter which JIRA issues get reflected back to Aha!
Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into...
Ely Greenfield
over 10 years ago
in Jira
4
Already exists
When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog
When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...
Deleting a feature or requirement should delete the linked Jira issue(s)
When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest
over 10 years ago
in Jira
11
Will not implement