I have a question about automating JIRA service management.
Are there any documents that describe processes that cannot be achieved through automation? For example, repeated processing is not possible, nested judgment processing is not possible, etc.
Hi @青山 明 ,
this is a tough question. There won't be a total summary available of what's not possible, because you have to update it nearly every week due to continuous deployment of enhanced or new features.
Repeated processing? It's possible. Nested judgment? It's possible. Solutions to be discussed on specific user story.
You will find solution where JIRAs REST API is called via automation to process specific tasks, which are not available as a one-shot call.
Thank you for your reply.
However, with JSM automation, there is a limit of 10 repetitions and it cannot be used. Also, nested judgment processing is not possible. Is there any evidence that it can be done?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @青山 明 ,
I think I have not understand your question by now.
Can we get one step back and clarify your subscription?
As you can see on page https://www.atlassian.com/software/jira/service-management/pricing
* single project automation is unlimited
* multi project automation has limits, depending on your subscription
While I've written there are no limits, I've had our premium subscription in mind. There are a limit for multi-project automation, but we don't need them by far.
When you say "repetitions" can you explain the rule a bit more, so I might understand it? What is the trigger event and what's the project scope (single / multi project)?
Thank you
Ingo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply.
For example, when parsing JSON data etc. in automation. When you have multiple pieces of data, you have to iterate over them, which is difficult. This is possible with scripts, etc.
Judgment processing is difficult to automate, but nested judgment processing is difficult.
Such processing is necessary when parsing JSON data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok, understand. At this point, we have developed our own (Forge) Apps for integration and external system integration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.