Stefan Salzl Community Champion

Hi @Gail As far as I got your requirement right the rule in the attached screenshot should deliver the expected result: Please let me know if this works and was helpful. Best Stefan

Hi @Stefan Peev is this in the scope of jira service desk? Where exactly are those requests created/where do they come from into your system and how is information (email, name, ...) inserted into description? Best Stefan

HI @Stefan Peev and welcome to the community, Could you specify/describe your requirement more in the scope of a use case? what is the problem you trying to solve? what is the entry point of your action? From the description I cannot follow where this happens, where does the email input comes from, etc.... In order to find…

Hi @[deleted] and welcome to the community, As the trigger of the rule is a version the inititial input (scope) to the rule is a {{version}}. So the condition right after your trigger fails as there is no issue. There is even a branch that covers all issues of a version. Please see attached screenshot. As far as I…

Hi @Gail How far did you get? Where exactly are you struggling? Could you show a screenshot of your rule and show us where exactly (date logic) the problems are? Best Stefan

Hi @DasJo I added your suggestion and (even if I´m not a fan of workarounds): It does exactly what it should. Thanks for leading me into the right direction. Best Stefan

Hi @Nic Brough -Adaptavist- thanks for your reply. I was thinking of indexing problems. It was just confusing for me as there is a seperate re-index post-function and I placed my scripted post-function after the re-index. Furthermore I added following line to my script: log.info("trigger-issue: " + issue.key + " status:…

this could be a feasable workaround. Thanks for the hint ;)

@Nic Brough -Adaptavist- any hints from you? Isn´t it possible that the previously transitioned issue is detected by the jql? --> when I transition Issue C to "Done" and a jql in post-function is searching for issues in status done currently Issue C is not detected by my jql. Isn´t the transition fully processed at the…

Hi @DasJo tried a sleep in my script - that didn´t solve the problem. still the jql misses the issue that triggered the script. eg: there are 2 issues in status "Done": Issue A Issue B Issue C is currently in status "In Planning" and is transitioned to "Done". The workflow postfunction should now detect all issues in…

Hi @DasJo , This is my script: import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.IssueManager; import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.user.ApplicationUser import…

Hi @David Weir and welcome to the community, for me it seems like a problem with screen schemes. Is the field end date configured in you edit screen? You could check this by efiting the issue manually and check if the field is available in the edit screen. Best Stefan

Hi @Ivor as your rule is using a branch it changes it´s context/scope of action to the issues that are found by the branch-condition: * the jql in your branch is selecting "ISSUE-B" * as the action is in your branch it is processed against ISSUE-B I would suggest to * change the branch to a "lookup issue" action with your…

Hi @Jürgen Wagner , a test case in jira xray is "just" a documentation of steps that need to be taken in order to test the SUT. As far as I got your requirement right the test case should discover if a precondition is already met. How should the test case know from the System under test? even if the precondition was done…

Hi @kdickason , unfortunately I‘m not very proficient with scripting either. I just started my journey and asked similar question. Nevertheless I got very good hints to start from in the following post: https://community.atlassian.com/t5/Jira-questions/How-to-translate-from-A4J-to-Scriptrunner/qaq-p/1998239 Just did small…

Could solve the problem with a lot of snippets and "try and error". Might not be the most professional script but as I am not a developer I am proud it does what it should: Still any feedback/hints for improvement appreciated: // gets the value of import com.atlassian.jira.component.ComponentAccessor import…

Hi @Marco Brundel , I would love to solve this with A4J. Unfortunately it‘s not an option as this is on Server and the plugin is not installed. Thanks anyways for your effort. Best Stefan

Hi @kdickason In case Scriptrunner is installed in your Jira Instance --> that would feasible too to solve this use case. Best Stefan

@kdickason right now A4J is only part of jira cloud. On DC/Server there is a paid add-on but this is planned to be added into Jira (same as in cloud) within the next month. see following link: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-will-be-included-in-Jira-Data-Center/bc-p/2042669#M6578 Best…

Awesome. You´re welcome ;) Please give it a shot and in case it works: Please consider to accept the answer in order to make it easier for other users to find the solution. Best Stefan

Hi @Jacques B , As far as I got your requirement right this is possible with an automation rule. * given (trigger)* issue is transitioned to STA * when (condition)* issue type = subtask * then* branach for parent * transition issue to IB Let´s give it a shot and let me know if you have any further questions. Best Stefan

Hi @Tatianna Volamena and welcome to the community, just to make sure we are on the same page: as I see in your rule the trigger is „when issue is created“ and not „when issue is cloned“. So let’s say there is issue A that geta cloned to issue B. which user is appearing as reporter right now in the cloned issue B? and…

Hi @kdickason What you see in the screenshot is the Automation for jira (A4J) feature. If you are on jira cloud this is feature is available by default. If you are not familiar to it yet I would recommend to read through the basics and trying to build some examples:…

Hi @Graendy Panthalasian Could you describe your use case in more details to be sure we are on the same page? A test execution itself is a jira issue that symbolizes a container for operating execution of several test cases. Within the test execution issue each executed test case is called "test run". Simply said: a test…

wow...even noticing the smallest details 🙌🏼 Awesome work @Bill Sheboy 

Hi @[deleted] , Just a few points I would suggest for investigation (if they haven‘t been done already: * does the jql provide the correct result in the search within the jira project? * Does the rule run in the same project that the jql is selecting? Otherwise: Is the rule configured as a multi-project or global rule? *…

One more thing I found during some research was that there can be set several restrictions (eg IP range). see the link below: https://kantega-sso.atlassian.net/wiki/spaces/KSE/pages/235601943 Could you please check if anything is set there? Best Stefan

Hi @Maulik Panchal , The screens are a „ordered display list“ of fields. Those screens can then also be added to screen schemes which define which screen appears on a special operation (view, create, edit). Could you confirm that you can see the field when you create a new issue manually within jira? Best Stefan

Hi @Angel Urumov and welcome to the atlassian community, the url needs to contain the correct key of your project you want to get the components from. As I see the project key that your call is calling is „XXX“. Is this key correct? Does a project with the key XXX exist? Best Stefan