Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Jira Cloud has a concept called comment properties which can be used via the REST API and automation for Jira.
Can I set comment properties via Exalate scripts? If I can't, can I create a feature request somewhere?
My use case: I am syncing comments from Azure Devops to Jira sub-tasks.
Once in Jira there is an automation rule copying the comments to the parent issue. But we also have a rule copying the parent comments to the sub-task issues.
Of course I want to avoid duplicate comments. A robust solution would be to add a comment property to keep whether this was a comment originally created by Exalate on a sub-task. Those comments don't have to be syncec back to the sub-task.
Hello, Charlie Misonne thanks for raising this on community!
Aren't all comments by default created via Exalate User?
If so, you may identify comments created by Exalate via author.
worst-case-scenario, it's possible to create comments via Jira's REST API, using
JiraClient
Like so: