Add a new idea Subscribe
Status Shipped
Categories Jira
Created by Matt Case
Created on Mar 30, 2016

RELATED IDEAS

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! defaults to Aha! assignee and is a source of confusion. 

It would be desirable to have a configuration setting for the integration that would allow for turning off the synchronization of assignee information in those environments where the users don't exist in both systems. 

  • ADMIN RESPONSE
    Dec 14, 2017

    We have launched an enhanced Jira integration. This integration will allow you to explicitly enable and disable individual field mappings including assignee, along with several other new capabilities including the ability to:

    • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
    • Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from Jira to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Paul Mundy
    Reply
    |     Jun 2, 2017

    My issue is we are a small company with 1 prod manager (me) and a large number of dev so we only have a very basic license. With that you can't set up even reviewers in Aha and as such I'm always the Aha assignee even when JIRAs get assigned out. 

    I'd like Aha to take in the JIRA assignee even if they are not in Aha (or at least allow me to create JIRA only users in Aha

  • Guest
    Reply
    |     Jun 28, 2016

    Hello 

    I also had this issue as a user but we have been getting around it by pulling a report that shows that assignee and then adding the Jira user in aha as a lower permission (reviewer). It has solved that issue you are encountering.