The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
1
0
-1
2 answers
- 210
Hi
Please try:
issue in under_sync_by_connection("Connection name")
and
issue in sync_stuck("Connection name")
The stuck will have the same functionality than a connection in error.
Thank you.
Kind regards,
Mathieu LepoutreAdd your comment... - 10-1
Hi Mathieu,
sorry but according to my knowledge issue in sync_stuck("Connection name") does not cover all existing error use cases and so does not fulfill our requirement.
Regards Michael
Add your comment...
To allow users from the business that does not have Jira system admin permissions and also no Jira DB access to view in a dashboard Jira issues that has currently a sync error for a Exalate connection that they are from business side responsible, a JQL function is needed that allows to search for issues that are under Exalate sync for a specific connection and have a specific Sync status, e.g. Error.
Currently we only know a JQL that allows normal users to search for issues that are sync_stuck, but that does not include issues with a sync error. So similar JQL function that reports issues under sync error for a connection would solve our request..Or even better a more general JQL that allows a connection and a set of Sync statuses as argument.