Ability to send static attributes to JIRA

Engineering has made many attributes in JIRA mandatory, which means I need to create custom fields. They would be OK with a static value that would identify it as coming from Aha!, as they want to make sure they are filled correctly manually but there's no way to relax the requirement for a specific JIRA user.

 

This would also be very useful to send attributes for Epics.

  • Daniel Hirschberg
  • May 6 2016
  • Shipped
Release time frame
  • Dec 14, 2017

    Admin Response

    We have launched an enhanced Jira integration. This integration will give you the ability to add constant field mappings, 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
  • Daniel Hirschberg commented
    May 6, 2016 22:47

    I should also mention that this would unblock our JIRA integration for Initiatives, which would be really useful.

  • Matt Cardwell commented
    September 23, 2016 20:25

    This would be very helpful to be able to populate component values in JIRA based upon the product in Aha! as there are some products that are managed separately within Aha! but feed into the same JIRA project.

  • Robi Chakrabarti commented
    November 8, 2016 23:31

    We have some products that are part of the same JIRA project, but different sub-teams.  Each sub-team needs to be set manually on each feature in Aha, and people are prone to forgetting. It would be very useful to have an attribute at the product level that can be applied to all releases, features, and requirements so they sync to the correct JIRA project.