Hana Kučerová Community Champion

Hi @Romain VELON , this is really strange. I've just tested it using my instance and it works. A few tips, what you could try: * getCustomFieldObjectByName is deprecated, use getCustomFieldObject('customfield_xxxxx') instead * check there is only one custom field with name "Number 1" in the system * add "Re-fetch issue…

Hi @Frédérique Cusson , it is not neccessary to have this row MutableIssue issue = issue in the script, you can remove it. I always add it, because it helps me to check the code in my IDE :-). In your case, I think you need to change the order of the post functions. The script should be executed after "Creates the issue…

Hi @Frédérique Cusson , I believe the problem is you just set the new values, but you don't save the changes. I did not test the code below, but it should look something like this: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.CustomFieldManager import…

I think, it would work, if you merge the rules and add "Re-fetch issue data" step between the actions. About the tick - it just means, that the rule will also react to the results of the another rules. For example - if the first rule does the issue transition and the second reacts to the issue transition, the second is…

Hi, I think it happens because sometimes the second rule is executed first. As far as I know, there is no possibility to setup the order of rules and there is no guarantee, that the first rule will be executed before second. What about to merge the rules together? Is it suitable in your case?

Hi @LIndsay Kiefer , I believe, this should work: issue.getIssueType().getName() When you try to log: log.error(issue.getIssueType().getName()) How does the output look like? Thank you.

Please try something like this, maybe you will need to do some changes, but it works for me. Just create custom listener - setup your project and event "Issue Updated". The provided script checks the changes during the issue update and continues only if "Text 1" field has been changed. Then then JQL is created based on the…

Hi @Romain VELON , if you have ScriptRunner, you can create custom listener for Issue Updated event. Is it suitable for you to have groovy script in your solution? Are you familiar with groovy or should I try to prepare it for you?

Sorry, I didn't understand your problem correctly, I thought it is a value. As far as I know it is not possible to compare values of fields like this, maybe there are some applications, but I'm not sure, if they will work with Automation for Jira. Is there any other way, how to identify the related issues?

Hi @Romain VELON , please look at "Branch rule / related issues" component. You should be able to select: Type of related issues: JQL ("External ticket Id" = "Text 1") Then edit all the related issues and setup link for them.

That's strange, it works for me :-( Just quick check - did you setup mapping for the behaviour?

Hi @James Breunig , The script is attached to the Downtime Start field, which means, that it is executed, after the Downtime Start field is filled in. When you create the issue, you probably first fill in the Downtime Start field, then the validator is executed, but the Downtime End field is empty, so nothing happens, and…

According to the documentation, there could be problems with "/", but numbers are not mentioned. Version 5.9.11 is quite old, it seems to me like a bug :-(...

Hi @Sam Chan , please try this URL (+ DELETE): https://yourinstance_confluence/rest/api/content/26083521/label/56789 I've just tested it and it works for me. 

Yes, this should be possible. 1) Create custom field with type User Picker (single user), let's name it CO 2) Create first automation rule, which sets the value of CO based on the selected Components (probably using several "if/else" and "then" blocks * if Components contains any of Component1 then edit CO: set User1 *…

Hi @Rosa M Fossi , I don't think this is possible using Automation for Jira. I didn't find any way to obtain the lead from the issue's component (just the component's name). According to the other posts it is not implemented yet. There could me more components and it is also possible some components don't have any lead, so…

Hi @YoSebi , please look at the Dynamic Forms - I believe it could be used in your case, but to be honest, I didn't try this functionality yet.

Hello, I've found two typos in your script: * ComponentAccessssor-> ComponentAccessor * customFfeld2 -> customfield2 I've changed your script a little bit, please try: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.fields.CustomField…

Hi, just tested the code below with the provided json, works for me. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.comments.CommentManager import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.util.json.JSONObject import…

Please, could you also attach your json file here? I need to know, how the structure of the file looks like, when there are more issue keys. Thank you.

Just replace "issue" with "issueObject" like this and it should work: commentManager.create(issueObject, loggedInUser, commentBody, false)

Hi, the first parameter in the create function must be issue object, but according to the error message you are passing String variable. You need to obtain issue object somehow. Where exactly are you trying to test this script? It is still the rest enpoint section?

Hi, you need to add something like this: import com.atlassian.jira.bc.issue.IssueService import com.atlassian.jira.workflow.JiraWorkflow import com.atlassian.jira.issue.IssueInputParameters ApplicationUser loggedInUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() CommentManager commentManager =…

Hi @Simone Croci, welcome to the Atlassian community! It depends which file you've deleted but I would definitely recommend you to clone your repository again to create the correct content of .git folder.

Hi @Dane.Foster , welcome to the Atlassian community! Please look at the documentation for Jira cloud - create issue section. The correct url is: https://valhala.atlassian.net/rest/api/3/issue Provided payload seems correct to me, but please check all the ids, if they are valid for your projects and issue types. I would…

Hi @Suresh Jambhalkar , yes, the access restrictions are not applied to the attachments. I don't think it is possible to change this behaviour using Jira cloud itself. I also tried to find some application, but I didn't succeed. If you need to restrict access to attachments, maybe you can store them to the linked issues…

Hi @PeteToscano , this is a little bit strange, I believe the resolution date should be set automatically, when the resolution is set. ScriptRunner for Jira has the Built-in Script, which is called Bulk Fix Resolutions. Maybe you can try it, if the behaviour would be the same or not.

Hi @Николай Киселев , this row seems strange to me: String jsonString = "body" I think the variable jsonString would contain 4 characters "body" not the provided json data.

Hello @gabriela.lobo , I believe you would need some kind of application like Extension for Jira Service Desk to achieve this. Maybe there are more options, how to do it, but I didn't find any more.

Hi @Romel , please look at automations in Jira cloud. I think this functionality could help you achieve, what you need - just add the automation rule defined like this: When: Issue created If: Field equals A Then: Edit issue field Labels -> set value B Else-if: Field equals C Then: Edit issue field Labels -> set value D…