Stefan Salzl Community Champion

Hi @Prajwal Ashok Nagrale and welcome to the community, How did you integrate SN and Jira? Are you using a Plugin? If so: which one? How are attachments sent to jira? Please share some more details regarding your problems. This helps the community to find a solution. Best Stefan

Hi @Boyd K I tried to reproduce your situation but the following automation rule worked fine in my system (jira cloud with github): Could you find any differences regarding your and mine automation rule? Best Stefan

Hi @Theis Joergensen What exactly do you mean "cascading select list" is not supported in automation? Furthermore for better analyze: Could you please share a screenshot of the whole auomation rule? Thanks in advance. Best Stefan

Hi @Timofey Prokhorov Unfortunately I´m out of xray license at the moment and can´t verify/reproduce any cases. As far as I know the test coverage section should be shown for all issues that are covered (I guess even if there are no test cases). Still: do all the stories have test cases linked? If so and the section is…

AWESOME job 🎉🎉 keep it up 💪💪

Hi @Ben R , yes this is possible as the smart value of this field returns a list of its values. You can check the size with the following smart value: {{issue.components.size}} to check wheter on creation or on field value change I guess you need to create 2 different rules as those are 2 different triggers. I hope this…

Hi @Brian Stephenson , what does the output of the audit log look like? could you share a screenshot? Furthermore: Smart values are case sensitive and as far as I know the „issue“ in „triggerIssue“ needs a capital „i“. could you please try the following: "customfield_10068": {{triggerIssue.customfield_10022}} Best Stefan

Hi @Sofia Lousada -- welcome to the community, so to get your question correctly: the field is required but it´s not shown in your screen so you can´t edit/fill the field? Best Stefan

Ok. Let´s take one step back and wrap this up. What exactly is the ende2end use case you are trying to solve? Could you please describe your situation/problem in a functional way from the very beginning to the expected outcome? Furhtermore one technical question: As far as I know the functionality of "linking jira issues…

Hi @Boyd K , Please try the following smart value: {{pullRequest.destinationBranch}} Furthermore for debugging you could add a "Log action" to write result of your smart value to your audit log to check if it´s correct. In case this doesn´t help please provide some details (eg. a screenshot of your automation rule and the…

Hi @[deleted] , This is still a technical description of what you expect to do. Unfortunately the native jira automation (A4J) can´t provide all of these with via smart value. Though the trigger of the automation rule is "when issue is linked" the context of the rule is not the event (like it would be in a listener with…

Could you please provide all details to make it possible for the community to investigate into the situation? What does your call look like exactly? What exactly is the outpout/response? etc. --> everything that could help to analyze your problem. Thanks in advance. Best Stefan

@Srinivas Ch -- welcome to the community, I´m not sure if the api request accepts a "filePath" option/property. did you try to use the whole path of the file in your "fileName"? "attachments": { "add":[ { "data":"whatever", "filename":"C:\andyDirectory\filename.txt", "contentType": "text/plain" } ] } Best Stefan

AWESOME 🎉 Thanks for your feedback.

Hi @Gentrit Cerimi -- welcome to the community, If this is the system field "End Date" (as it looks like in the screenshot) the jql needs to be the exact same string as the field´s name. Try the following jql: "End Date" < now() AND status NOT IN (done) Best Stefan

Hi @[deleted] you are welcome ;) Could please explain the problem you´d like to solve from a functional/use case perspective (wihtout mentioning the technical solution). (eg. in a given-when-then scenario) Furthermore I got you so far that the trigger is a issue-linking. Please keep in mind that the issue linking is an…

Hi @[deleted] Isn´t this a duplicate of this post ? Best Stefan

AWESOME 🎉 good to know you got that working 💪

Hi @[deleted] , What the rule in your screenshot is trying to fetch are smart values provided from the issue from the trigger. Smart values do not exactly provide the same data than an api call. According to this documentation "fields" is not a provided smart value of an issue. I don´t know the whole use…

Hi @Tony Conteiro , As far as I got your requirement correctly the following rule should do the work. Some details for description: the "current issue" branch will still refer to the trigger issue. Therefore I added another epic-branch to split up the 2 actions. In the 2nd epic branch the rule checks if there is any task…

AWESOME!!! Good to know you got that working 💪🎉

Hi @Nitzan Matalon and welcome to the community, do I get it right that once your automation rule 1 updates the story (with its subtasks-estimate-sum) the 2. rule should be triggered and do the same for the epic with its stories? If so: In your 2. rule‘s details did you check that the automatiok rule is allowed to be…

Hi @Nofar Ben Kereth , What exactly do you mean with "pre-defined"? Pre-defined by yourself so you can use them as kinda template? and furthermore: How do you copy projects? Could you explain this use case a bit more in details? My personall suggestion/quick win would be to export the required automation rules and import…

Hi @Florencia Bravo - welcome to the community, are you using any testmanagement plugin? is the workflow/status the native jira workflow status or is this specific to your test management plugin? Best Stefan

Hi @Justi Lawson , Do these 2 fields have any dependency or are they losely integrated? furthermore: How/where would they like to call/submit the store number? On issue level? Where do the want to retrieve the information from? The point is: A custom field could be filled with information in each issue. If they have no…

@Mélanie Liguet awesome 🎉 great to know it‘s working. Thanks for the reply.

Hi @Tommy Augustine , the screen refers to your action regarding an issue. So to say: No, this doesn‘t affect if a field can be edited or not. If a field is added to the „create“ screen it means that it will apper in the mask when you create an issue. If it is not in the create screen you could not edit or add value to the…

Hi @Joshua Tilton Regarding your 3rd condition: Could those issues that should trigger the release be in different projects? furthermore: within your release version action there need to be declared a project where the version should be released. how is the action configured? Did you check/can you make sure that the…

great job @Jessica Kizmann 💪🏼 good to know you got that working. Please consider to hit the accept button in the answer in order to mark this post as resolved and make it easier for other users to find a solution in case they are faced with a similar problem. Best Stefan

mkay. just tested this in my site and could only do it with the ID. usually i get such information via the API. So in this case I chose the needed option in an issue and did a "get issue": <your_domain>/rest/api/3/issue/{issueIdOrKey} This will return a JSON of your issue. You can then search for your custom field and it…