Skip to Main Content
Status Planning to implement
Categories Integrations Reports
Created by Guest
Created on Feb 27, 2018

Filter on JIRA ID / JIRA Key attribute in Reports

The JIRA ID and JIRA Key are reportable attributes within Aha! but they currently cannot be filtered in the reports.

Sometimes where a JIRA ID or Key are known, it would be useful to filter/search Aha! to find this information.

Release time frame 1 month
  • ADMIN RESPONSE
    Sep 23, 2022

    While it is not currently possible to filter by ID or Key, there is an easy workaround to find records that have not been linked via an integration.

    Using a list report:

    1. Add the integration record type to the report (to include the integration name for example)

    2. Add the filter Integration > Integration webhook user

    3. Set the filter to 'Is blank"

    This will filter out any records that have been linked via an integration.

  • Attach files
  • Christian Hartmann
    Reply
    |
    Jul 26, 2024

    After 6.5 years - Yee-haa. Better later than never. Thank you Aha for "not" forgetting about this.

  • Guest
    Reply
    |
    Feb 11, 2020

    This is a super important feature for the reasons mentioned above in comments.  

  • Guest
    Reply
    |
    Jan 21, 2020

    The ability to report on synchronicity between Aha and Jira is massively hampered by not having this feature. 

    If we assume the Aha-Jira integration is set up correctly, then the only aspect we need to worry about is if the record in Aha has a Jira Key associated.

    I am looking to produce live reports in the list and chart format, with all the Initiatives and Master Features that have not been synchronised with Jira. The best way to do this is to filter by Blank Jira Key.

    At the moment I can only produce a list, which is sorted by Blank Jira Key at the top, then all other initiatives with a Jira Key beneath this. Whilst it does do the job, it means I cannot do visual reports on this, or slice the data so it is much more digestible for those I'm sending the report to.

  • Michele Oliveto
    Reply
    |
    Nov 1, 2019

    We need this capability as well for data quality validation to to identify Initiatives that have not been synchronized to Jira.

  • Chris Horne
    Reply
    |
    Oct 2, 2019

    Not being able to filter on Jira ID/Jira Key is seriously hampering data quality reporting for us. I have to export reports to Excel and trim them there to focus only on Features that have been synchronized to Jira. Please make these fields 'first class citizens' from a reporting perspective by adding the ability to filter on them. : )

  • Guest
    Reply
    |
    Mar 18, 2019

    I'm the Aha admin and deal with a lot of producers who want to be able to pull list reports together for their idea and features that have not been promoted to JIRA tickets (aka checking tickets that still need to be actioned). 

  • Guest
    Reply
    |
    Sep 7, 2018

    Filtering based on null or non-null Jira Key or Trello ID would be enough for me.

  • +2
6 MERGED

Allow users to filter or calculate on the Jira Key in reporting

Merged
We have our products set up with a Jira Integration. We'd like to be able to report on those requirements that are in progress that are missing a Jira Key. Ideally this should not happen, but we have found that it does from time to time. So it wou...
Guest almost 5 years ago in Reports 0 Planning to implement
28 MERGED

Allow integration records to be filtered in a list report

Merged
As a PM, I'd like to keep track of items sent to our Dev tool (in our case, JIRA) and I would like to have the ability to create a list report of items that exist in JIRA right now. If I had the ability to filter by JIRA URL, I could easily see wh...
Greg Koeka almost 6 years ago in Application 2 Planning to implement
13 MERGED

"Sent to jira" filter

Merged
Add "sent to jira filter" :true/false, so it`s easy to spot the feature which are not synchronized to jira. Now It`s needed to go thought features one by one.
Szymon Lukaszczyk about 7 years ago in Jira 1 Planning to implement