RELATED IDEAS
Add filters to integrations to prevent sending records that meet criteria
It would be useful to be able to create filters to prevent certain records from being sent to Azure, JIRA, or other integrations. For many workflows, there may be "raw" working records in a release backlog that are not ready to go to engineering teams; these would only serve to clutter their working backlog.
The lack of some type of filter becomes an issue when syncing release details (resend all fields). Since neither Azure or JIRA will sync their internal field used for ordering work items, we have to use a custom field to see the Aha rank within a release (separate issue). We see this often when placeholder stories are added to the backlog that are used for tracking Work Type allocations.
If we were able to create a filter on the tags field for example, we could stop from sending records with a specific tag to the integration and prevent the clutter/bloat in the engineering workflow tool; also preventing the admin time to clean it up.
We do that as well. However, since the Aha! Rank is not updated for all items in a release/backlog when a card order is changed, it leads to multiple cards with the same rank being present in the engineering tool. Resending the release fields was the workaround provided for that and conflicts with this workaround.
Thanks for the idea!
We will continue to monitor this idea for community feedback.
As a workaround, some customers will either send records one by one through the integration as they are ready or use a parking lot release until you are ready to move into the active release.