Integrations 2.0: Support importing unmapped issue types
In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types.
This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha!
This is important, without this we have no way t...
Integrations 2.0: Support JIRA Priority field mapping
In 1.0 I could map a custom field to the priority field in JIRA.
In 2.0 it appears as an option but the Aha! fields it can map to are only the name/description. It doesn't allow mapping my custom field to the JIRA field.
Integrations 2.0: List view bulk edit Send to for integrations 2.0
Integration 1.0 integrations have the List view option for bulk editing Send to ----.
The integrations available to send to do not include 2.0 integrations.
2.0 integrations should be supported for bulk sending operations just like 1.0 integrations.
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
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...
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...
over 6 years ago
I wish I could have this option:
Master Feature > Solution Capability, Feature > Feature, Requirement > User Story
This way I could send overview-level requirements and portfolio groupings over to my friends in delivery.
My workaround ...