RELATED IDEAS
Allow To-Do's to be mapped to JIRA Issue Types
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 Requirements but we think it would be very benificial to be able to create To-Do's and link them to sub-tasks. This working method makes a lot of sense, especially if To-Do's could be linked to Requirments within Aha.
The current issue is that Aha recommends that we map Requirements to sub tasks, but this doesnt make logical sense to my development team - they feel that requirments should be requirments and that there should be a list of tasks associated with a requirement that works towards a complete feature.
-
ADMIN RESPONSEJan 21, 2016
Our recommended configuration for JIRA Agile users is to set the data objects up in a similar manner to how you have it (with exception to Requirements - as you've described).
While we can understand some discrepancies with the team, we feel that this set up allows for the greatest flexibility and has been reinforced from community feedback.
At this point, we do not have plans to allow To-do's to be integrated as this is a less flexible object and will not provide the capabilities available to requirements. Combined with current priorities, it is unlikely that we implement this in the near term. We hope you can understand.
4
MERGED
Synchronising to-dos from JIRA
Hi, In addtion to using for JIRA for managing our features/requirements. We also use it to manage general product development activities (not necessarily directly related to development - more related to project management e.g. setup test environm...
0
Unlikely to implement
1
MERGED
Availability of Aha To-Do's for integration with Tasks in JIRA
When we create Features (epics) and stories in Aha, a lot of times, we have discussions on some key things that need to be done by the development team while coding for it. Today, we have to put comments which they then create tasks for and then l...
0
Unlikely to implement
3
MERGED
Bi-directional mapping of Feature 'To-Dos' with JIRA Project 'Tasks'
To-Dos for new product development can be assigned to development teams using JIRA to track their work on projects. This integration would allow developers not engaged in new product development to receive task assignment related to the project in...
0
Unlikely to implement
1
MERGED
Jira Integration: ability to map to-dos to sub-tasks
We utilize Jira & Aha! across our organization for our development and product teams and have just implemented an integration to simplify our ways of working. We'd like to be able to map To Dos in Aha! to Sub-tasks in Jira. Is this something t...
0
Unlikely to implement
While you say that the above description is recommended, the reality is requirements are the equivalent of a story and to-dos are the tasks. Not sure what the technical challenge in opening this up would be but it gives flexibility to every type of setup. i can understand if it introduces any other limitation or issue but doesnt seem to be the case.
We would also like To-do's to be mapped from Aha to JIRA. There is lot of context and discussion which happens in To-Do's in Aha and unfortunately all of them are missing in JIRA. This includes the approver details as well.
We would also benefit from the ability to map the Aha To-Do's into JIRA. For this software to gain traction in our business we need flexibility to adapt it's use with existing tools.
Hi
Jira is my single task management tool with multiple Jira projects being viewed in a single personal to do list. Obvious with much content coming from/ going to Aha.
It is convenient to capture To Do items immediately in Aha but I’d like them to then appear in my Jira task list.
This would be across multiple Aha products not just one.
Is there any way to do this?
Unfortunately this is a deciding factor to continue using Aha in the future. Our team centers around JIRA and unless we're able to configure Aha to work the way that works best for us we're going to have to find an alternative solution for tracking our Roadmap.