Skip to Main Content

Share your product feedback

Status Future consideration
Categories Jira
Created by Daniel Pokrývka
Created on Aug 27, 2019

"Make everything OK" button on feature that triggers insert/update/delete/move JIRA->AHA

Hello,

it would be very helpful if in scenario, where aha records are linked to dev tool records (e.g. JIRA), there would be a possibility to trigger full record update for a single record.

Example:

  • integrations config:

    • Features linked to Epics in JIRA,

    • Requirements linked to Stories (and bugs, and spikes..) in JIRA ,

    • Releases are synced to FixVersion in JIRA

  • integrations configuration has changed - multiple reasons possible:

    • new mappings,

    • new JIRA custom field,

    • new fields set up for sync (e.g. time tracking)

    • stories moved in JIRA from one epic to another (JIRA does not fire "epic link changed" event)

  • there is a discrapancy in between AHA/JIRA due to some error

When situation described in example occurs, there is a need to update features in AHA based on JIRA data. There are two ways how to do that now which I am aware of:

  1. go to product config / integrations and push button "update records"

  2. go to product config / integrations and use import/update from dev tool functionality

  3. go feature by feature and use method of multiple steps> 1. unlink, 2. link JIRA item, 3. see what stories from JIRA where not pulled up, fix in JIRA, repeat

Option 1 make the whole JIRA project to be synced with AHA, which can take many hours and I would argue no one needs to run update on items older then few months.

Option 2 is slightly better, however it is not very user friendly as coming up with JQL query in an already improperly synced AHA-JIRA scenario (e.g. you can not rely on FixVersion in JIRA)

Option 3 is quite use click excessive and time consuming

Very nice would be to have an action on feature level, that would basically do "update records-from {linked time}", but only in scope of the single feature and its requirements:

  • it would update all fields on feature itself based on JIRA

  • it would update all reqs linked to JIRA stories etc., including all fields

  • dtto for subtasks if in use

I think there must be many aha addicts who would appreciate this feature. At some point every aha addict decides to start using capacity features and start pulling up estimates or at least work logs, changes integrations field syncs, adds custom fields, need to update something because of mess in one or other tool. Hope the community does not let this feature down :-)

P.S. This idea will either solve or help in case of similar ideas here:




  • Attach files
  • Daniel Pokrývka
    Reply
    |
    Oct 10, 2021

    Today I had to run re-sync of AHA workspace (features, requirements, ..) linked with Jira project just because I noticed that requirements were not updating for some time (few hundreds).

    I will be waiting for few hours before this finishes.
    Type: Update all linked records
    Date/Time: 10 Oct 04:28pm
    Status: Running
    Description: cca 13% after 20 minutes

    Could you please consider creating this "Update all linked records" on a feature itself? So that I can fix few features instead of resyncing a project with potentially 1000+ requirements, 300+ features etc.?

    This is really painful.

  • Daniel Pokrývka
    Reply
    |
    Nov 5, 2019

    One problem solved (not all) - epic link update in JIRA:

    Epic link update on story level in JIRA solved by Attlasian - event gets fired properly. See versions and details (both server and cloud version): 

    https://jira.atlassian.com/browse/JSWSERVER-12299
    https://jira.atlassian.com/browse/JSWSERVER-11149
    https://jira.atlassian.com/browse/JSWCLOUD-15973

  • Daniel Pokrývka
    Reply
    |
    Aug 27, 2019

    Found few ideas that my idea would help .. decrease pain :-) 

    3 for one.. ;)

  • Daniel Pokrývka
    Reply
    |
    Aug 27, 2019

    Ahh .. I suspected so, Austin. My original half-one-liner probably made zero sense :-)

  • Admin
    Austin Merritt
    Reply
    |
    Aug 27, 2019

    Hi Daniel, thank you! For some reason the original idea only included part of the first sentence. But now I can see much more detail. This makes sense now that I can see the full detail and example.

  • Daniel Pokrývka
    Reply
    |
    Aug 27, 2019

    I have simplified the summary name for the idea to give more clarity.

  • Daniel Pokrývka
    Reply
    |
    Aug 27, 2019

    ad  We do not provide this current since records are updated automatically when changes happen in the development system.

    This does not apply to the situations I have outlined. Please see the description with example.

    ad Are you requesting the ability to update a single feature based on the linked record in the development system

    Yes.

  • Daniel Pokrývka
    Reply
    |
    Aug 27, 2019

    Hi Austin,

         can you please specify which part would you like to clarify based on my long description? I can meet with you today, if you want.


    P.S. I just had meeting today with Perry Hurtt on the topic.

  • Admin
    Austin Merritt
    Reply
    |
    Aug 27, 2019

    Hi there, thank you for your idea! Are you requesting the ability to update a single feature based on the linked record in the development system? We do not provide this current since records are updated automatically when changes happen in the development system. Could you please clarify your use case to provide more background on what is needed? Thank you!