Stefan Salzl Community Champion

Hi @Jack Etzion and welcome to the community, Assuming your Jira is connected to your github and an issue is "linked" to a branch: As far as my knowledge reaches I guess this can be done with firing a webhook from github when the pullrequest is created with a reviewer (see link below):…

Hi @Amit Srivastava Any feedback to this ? Best Stefan

Hi @Sofia Grunspan Could you describe this in more details? From which issue would you like to copy the custom field? As far as I can see from your rule there is only the trigger issue and the cloned issue. If you clone the trigger issue the group picker field will be copied/cloned anyways. Please let me know if I got…

Hi @Alex Baker If i got your requirement right this can be done with workflow validator. To do this you have to go to your workflow for subtasks, change to edit mode, choose the desired transition and add a validator (see screenshot): Best Stefan

Hej @jamie , In case the situation you described was the problem could you post your solution as a separate answer and accept your answer so this iasue can be marked as solved and make it easier for other users to find the solution? Best Stefan

ah...I didn‘t notice it‘s writing exactly the same message twice. please appologize 🙏🏼 hmm....that looks really weird indeed. could you please share a screenshot of the audit log? what does the jql look like and what is the result? Best Stefan

Hi @jamie , couldn‘t find your „pull_request.actions“ in the payload. Could you also write those values that you are comparing to the the action log? Furthermore: Are the compared against string or boolean true? Best Stefan

Hi @Anudeep Patel and welcome to the community, could you provide information how far you got with the instruction you mentioned above? Furthermore could you please share your API calls? Is there any error message occuring? If yes: which one? Best Stefan

AWESOME!!! great you got that working 👌🏼🥳

Hi @Jacques B Please apologize my missleading answer. My bad :-/ It´s not a matter of the screen scheme but of the field configuration. If a field is set required in a field configuration and (only) this configuration is used in a project this is valid for the whole project. This could be solved by setting up 2 different…

Hi @Jacques B as you mentioned there is only one screen I assume there is no issue type screen scheme configured. Therefore: the 1 existing screen is valid for all issue type. So to say: if a field in the screen scheme is required it‘s required for all issue types. I would suggest to configure different screen schemes and…

Hi @celeste.valambhia Please consider to accept the answer if this was helpful in order to help other users to find a solution in case they are faced with similar problem. Best Stefan

Hi @Rafael Antonio Sbroglio mainly boards in jira are only views based on a filter. An issue is always created within a project but not on a board. so the questions are: * Are you using two different projects for these issues? * when would you like the 2nd issue to be created? —> in general it‘s possible but every…

Hi @Chiranjeev Singh , assuming I got your requirement right this should be possible: * trigger* issue transitioned * Condition* when linked issue of specific type is present * branch for linked issue (of the specific type)* action: transition issue to status from trigger issue Best Stefan

YIIIIIIIIIIHAAAAA!!!!! Great job folks 💪🎉

AWESOME!!!! Good to hear you got that working 💪💪

Hi @Felipe Fernandes As the documentation quotes {{issue.epic}} only works for issues that are added to an epic (so to say to get information from the "parent-epic"). In case the epic itself triggers your rule its scope is already on the epic issue and "Epic Name" is a field within the issue. Therefore the following smart…

I would ask the question more likely from a "testing process" perspective: What is the difference between smoke and WiFa? Is the SUT the same one? and also the same version? If so then the question from my last post still stands: how can one and the same test case on one and the same test system be passed and failed at the…

Hi @Joseph Aragones The link you provided in your original post leads to/describes the jira native importer. Multi value field imports are supported with jira native importer. According to XRAY importer documentation multi value fields are not supported (see the link below):…

Hi @celeste.valambhia and welcome to the community, Could you please share a screenshot of what you see? As far as I know this view depends on a configuration wheter to show latest execution or a specific version, etc.... furthermore one question comes up for me: assuming both test sets run within the same version/test…

AWESOME!!! Good to know you got that working 💪💪 Best Stefan

Hi @Chasovskikh Kirill as far as I understood you described 2 different scenarios because the first one would obly be an „if“. There is a special „for each“ branch that would create a subtask for each value while iterating over a field or a list. I recently answered a question similar to your requirement. See the following…

Hi folks, I´m aware of these things and sure do I recommend those things. The point is: this is not a personal requirement but from customer´s legal/audit regulation =S Thanks anyways for your input. At least I know it´s not possible "out of the box" :) That´s a clear statement. Best Stefan

Hi @Jarosław Kaczmarek the user fields (like reporter, assignee,...) need the user´s accountID to be filled with. Therefore I would suggest to fire another API call (before the create issue) to retrieve the accountID via the user´s email. Best Stefan

Aaaaawesome @Elif Alverson !!!! Great work 👌🏼💪🏼 Good to know you got that working. Best Stefan

uuuuh.....thanks for the hint @Elif Alverson . There was is a mistake in my screenshot. The first transition action right after the trigger is wrong.... =S furthermore: no - the trigger doesn´t say anything about which issue is checked. It just listens for a transition of issues in the projects that are in scope of the…

Hi @Elif Alverson , in case this was helpful and solves your problem please consider to mark the answer as accepted in order to help other users to find the correct answer in case they are faced with similar problems. Best Stefan

Hi @Elif Alverson , thanks for the information. that was really helpful. Please see the screenshot below. I just created it within 1 project and with other status. With some changes (scope needs to be multi-project to cover project X, Y and Z as well as your status) this should do the work: Hope this was helpful and…

I guess where @Kian Stack Mumo Systems wants to lead with his question is „can you see the field when you CREATE an issue in the gui. Fields depend on the screen scheme. If the field is not added to your „create“ screen the automation is not able to fetch the field either. Could you share a screenshot of the audit log…

Hi @Elif Alverson , thanks for the information. that was really helpful. Please see the screenshot below. I just created it within 1 project and with other status. With some changes (scope needs to be multi-project to cover project X, Y and Z as well as your status) this should do the work: Hope this was helpful and…