Stefan Salzl Community Champion

Hi @Richard den Dulk , Originally I have "only" been a scrum Master too ;) It´s not about another add-on. The RestAPI is something that exists already within your Jira. If you have engineers in your team or an admin by your hand it would 'only' be creating an API call that you than could include into your automation rule.…

@Ricardo Marques you are welcome. It‘s my pleasure ;) Best Stefan

Hi @Evan Smith In general it´s also possible to assign users to subtasks the same way as standard-issue (on the parent level). Could you please show a screenshot of your automation rule and where you got stuck as well as a screenshot of your subtask (maybe the subtask or its screen is configured in a way so that the…

Hi @Ricardo Marques As I am not an XRAY employee/engineer I can´t confirm this 100%. I only see the same documentation :-/ In this case I would recommend to contact XRAY vendor support directly. They are quite eager to help. Furthermore you could try by your own by checking which fields you can see in the workflow editor…

YEEEEAH!!!! Great job folks 🎉🎉🎉🎉

Hi @anna Could you check my answer and give it a try? Any feedback? Best Stefan

Hi @Richard den Dulk Could you try the mentioned options? Any feedback from your side? Best Stefan

Hi @Ricardo Marques , First of all unfortunately (as far as I know both tools) this can not be achieved via built in functionality. But (just a guess): I can imagine this could be done with some more development effort using API calls and/or Scriptrunner (in case scriptrunner plugin is installed). Best Stefan

Hi @a.moldavantsev This can be achieved with a scheduled trigger: Trigger: scheduled (every day, perform a query of issues that match date in your custom field) Action: transition issue (to expected status) Best Stefan

Hi @Amir Katz (Outseer) , try to convert the smart value/variable to a number with .asNumber see the description in the link below: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Best Stefan

AWESOME WORK 🎉🎉🎉

Hi @Richard den Dulk , As far as I am informed this is not possible with native A4J. I guess there is a way to do this with an API call out of your automation rule. This needs a bit more of "development" effort than just a simple automation rule. (see following…

Hi @anna and welcome to the community, some time ago I answered a question here that sounds similar to your problem. See the link below. I hope this helps: https://community.atlassian.com/t5/Jira-Software-questions/Deployment-info-feature-not-working-for-Github/qaq-p/1981719 Best Stefan

Hi @Alex Shirokov Could you please share your screenshots in a clean manner? (I guess issue names and/or status names are not sensitive data). This would make anylaze a lot easier for the community. Furthermore could you please also add a screenshot of your whole automation rule and also the action that processes the…

Hi @Alex Shirokov , could you check the workflow scheme? Regarding the description my first guess would be that parent issues are using a different workflow (thus: status) than subtask. Therefore it might be that subtask could not be transitioned to that specific workflow status. In case they are using the same WF please…

@David Fischer thanks for reaching out. Unfortunately this is not an option at the customer site :-/

Awesome job 🎉🎉 keep it up 👍🏼

@[deleted] that‘s the spirit 🙌🏼💪🏼 welcome to the community 🙌🏼

Hi @Robin Taylor , regarding your first requirement (as far as I got it right) all the necessary issues should be linked if eg. bugs are configured in your test/requirement coverage settings. eg. there is "BUG A". Within that bug "TEST_01" is created that is covering the bug retest --> therefore the test is linked to the…

Hi @Jeremy Cupps , could you solve the problem? Best Stefan

Ok. Thanks for your input and help. If it´s OK for you I would leave it open. Maybe I can gather some input regarding the API idea. Best Stefan

hm.....mhm.... that was the only thing I could think of too. Just would like to avoid alsways adding new customfields into issues not needed by the business but to build workarounds for jira functionality 😕 any idea if this information can be gotten via RestAPI ?

it´s the jira maaaaagic ✨✨✨ 😂😂😂 No need to apologize. It´s my pleasure to support and I´m pretty happy you got that working. Great job. Best Stefan

@Ajda Gruden Furthermore reagarding the status/boards: Boards are only views based on a filter. So (assuming SEO To Do and SOCIAL MEDIA To Do are several status) you would not need the labels. You could just move the special subtask immediatly to the required status and (assuming boards are based on status) shown in the…

@Ajda Gruden Please open the details of the audit log by clicking "show more" Best Stefan

Hi @Ajda Gruden Is there some field-edit-action within the creation of the subtasks? As the screenshot shows there might be some initial setting when you create the subtasks. Could you please also show the content of the actions as well as the audit log? I tested the behaviour within my site and it worked fine. I also…

Awesome. Thanks for the feedback and great to know you got that working. Great job 💪💪

Hi @SputnikCZ , smart values are case sensitive. As described in you post the field is spelled with upper case „S“ (Striking) but your smart value is lower case {{issue.striking}}. Please try to change the smart value to issue.Striking In case this doesn‘t solve the problem please share a screenshot of your automation rule…

Hi @Ajda Gruden What problem would you like to solve with your rule? Could you describe this in more details maybe with a use case and/or example? Please also share a screenshot of your automation rule. This helps the community to get a better understanding of the current situation and further analyze the problem. Best…

Awesome. Thanks for your feedback and great to know you got that working.