Filter Activity Stream by Component

[crivetechie]

The current behaviour of the plugin is to provide a summary of the opened issues filtering by component (jira/component) and project (jira/project-key) as well as displaying the activity stream for the whole project.

Would it be possible to make it so that the "Activity stream" shows only the activity for the issues related to the Component identified by the annotation jira/component rather than displaying the activity for the whole project jira/project-key ?

[Irma12]

Hey @crivetechie thank you for being proactive, we have investigated possible solutions and unfortunately filtering activity stream by component is not supported at the moment(https://support.atlassian.com/confluence-cloud/docs/add-the-activity-stream-gadget/) so we won't be introducing that improvement now. However, we will certainly try to find some workaround in some of the future iterations :)

If you feel like this is something you would like to contribute to, we would be more than grateful :)

[Irma12]

Hey @crivetechie we have been looking at this again and wondering if it would make it easier if you have option of having Activity stream completely removed from the card? If there is no use in having it the way it is now, do you think completely omitting it would make it a bit cleaner?

[crivetechie]

@Irma12 having the option to completely remove the activity stream makes sense! Thanks

[Irma12]

Added in new repository https://github.com/RoadieHQ/roadie-backstage-plugins/issues/171

[callmegar]

+1 on this, removing the activity stream is good in this situation, another option could be to add an Epic and pull only issues from a specific Epic into the activity stream

[ivangonzalezacuna]

I've been testing an option to filter the activity stream and I think I found a solution for it.

In our company's JIRA instance we have a filter by issue-key, so I changed the issueTypeCounter to a paged request getting only the issue key and the issue type object to reduce the amount of data. Then I use a .reduce() to make the count as before and, finally, I store a list of issue-keys. That list will be used to fetch the stream instead of the project key:streams=issue-key+IS+(list of issue keys). I also found out the confluence activities might be filtered out as well, at least for our case.

If you want to, I could create a pull request for that, I guess it's the only possible option to filter the activity stream right now, but only if your company has the issue-key filter available.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.