Hello everyone, I am trying to create an automation template for User Stories templates.
I have tried creating multiple automations, by adding a specific Description but it doesn't seem to work.
This is the way I have tried doing the automation.
We are using a company-managed project.
I have written a user story in this format and it worked fine, so I don't know why it's not working.
Any help would be appreciated, thank you :) .
First of all I can confirm that on my end, using markup on the description fields works fine. My suggestion would be to check first and foremost the audio log of the rule. What does it say?
The audit log says the status is SUCCESS (rule completed without errors and performed some actions successfully), but on my end I can't see anything when creating a new story.
Are you also using a company-managed project?
Also, I am not sure what actor I should choose, I am always choosing "User who triggered the event".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Aahh!
You have to make sure that the user who creates the issue, has also edit permissions.
When YOU try to create a new issue, is this rule working?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, when I try to create a new issue, the rule is not working. And don't know where else to check, or how to check the edit permissions :).
We are quite new to Jira so we're still learning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try to change the actor to "Automation for Jira" and try again.
Permissions are set on Project setting > Permissions
However, priori of changing any permission, you should check that the permission scheme does not affect any other project. Share a screenshot of it if you want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using for now the Free version. This is how the permissions look like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you change the actor as well and tried it again?
Please post your rule as well as your audit log from the last success or fail issue, which the description didn't change.
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.
Did you change the actor as well and tried it again?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the status Config change status is after I changed the actor and still doesn't work.
Can you share please an example of how you have it? Probably I am missing something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you change anything on the field configuration for the description field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looking now over detailed Audit log, I can see that under Success I see this.
Opening that story displays the template I have created. It was created by another user.
But I don't understand what means, If block.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Share a screenshot of your IF component.
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.
No, that shouldn't be the problem. It is correct. The "If Block" will evaluate if the issue type is a Story. If that fails, then it will evaluate the "else block". So we are good.
I would propose to delete that if block and create a new one, or add an "Issue fields condition" instead of and if-then-else component.
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.