Stefan Salzl Community Champion

Mainly the tough part of automation is to really be sure about the concrete use case/requirement, the specific conditions and specific action regarding use case and conditions. "random behaviour/conditions" is the opposite of automation. Are there any special cases where it can be specified which of the fields should be…

aaaah.....okay. Guess the easiest way that comes to my mind would be to set default value '0'. Would that be a feasible way? Best Stefan

Hi @syee , for better understanding and analysing: Could you please provide * screenshot of your automation rule * Information regarding type of the field "collaborators" Best Stefan

Hi @John Bolton The only thing that comes to my mind would be to add a custom field that calculates the difference between the 2 values automatically (eg. on update of the fields) and populate this custom field in your dashboard. Hope this helps. Best Stefan

Hi @John Bolton , As far as I know subtask should always be shown automatically (default board filter presumed). In my case this looks like this: Could you provide screenshots of * your board * your issue containing subtasks * board settings Best Stefan

@George Apostolopoulos Were all the configuration set correctly? Does it work now? Best Stefan

Hi @Matthew Pears , I could reproduce this behaviour in 3 ways: * adding a field that is not configured as numeric field * One of the custom fields of the calculation is not associated with the issue type/screen scheme * One of the fields in the calculation is empty Hope this helps and helps solving the problem. Best Stefan

Hi @Peter Hernandez 1. Saturday/Sunday According to this documentation * endOfWeek() --> Saturday * startOfWeek() --> Sunday Guess this would go into your first part of the jql with something like ...OR create in(endOfWeek(), startOfWeek())... 2. JQL/conditions (in case of automation rule) I would suggest to check some…

Hi @Craig , I tried to create a rule that fullfills your requirement (as far as I understood your need correctly ;) ). Please be aware that your rule need to be a multi project or global rule as it needs to operate across 2 or more projects. By using smart values the rule can check for issues in project X containing the…

Hi @George Apostolopoulos , Did you follow the instruction on atlassian support site: https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/ After installing the app and setting configuration the connection works perfect in my system. Git-related things are shown in my jira issues. All git…

Hi @Jayaprakash , There an option to set defect default vaules. See xray documentation: https://docs.getxray.app/display/XRAY/Miscellaneous#Miscellaneous-DefectDefaultValues As the docu points out not all of your fields can be pre-filled/configured. Maybe there is an option via API. Please don´t hesitate to contact vendor…

Hi @Ashim Upadhyaya and welcome to the community, I really tried all different places and sections in xray to figure this one out - unfortunately and really surprisingly (I was convinced this is possible) I wasn´t able to find a solution (at least not with jira inside possibilities --> I guess there are more advanced…

AWESOME!!! You are welcome. Good to hear it works :) Best Stefan

I just tested the following automation rule in my system. * field "Real start" is a custom field of type date picker * field "Years of usage" is custom field of type number * field "Expected End Date" - custom field of type date picker I just filled in Real start and years of usage --> Expected End Date was calculated and…

You could also use the value of your "Deprication period" use as the number in the brackets. Try following: {{issue.Asset - start date.plusYears(issue.Deprication period)}}

Hi @praveen rathore and welcome to the community, This section is meant to show imported results (if there are testcases from type automated). Nevertheless it´s not meant as an test automation tool but test management tool, manage test cases, traceability of tests and test results. Please see the documentation for deeper…

You are welcome ;) Please consider to accept the answer in order to this solution can be found easier by other users in case of having the same or similar question. Best Stefan

see my previous answer. An automation rule/action always refers to a context (you can see it like a variable) named issue (that reaction then can refer to). When a rule is triggered by an issue the {{issue}} is automatically set and handed over to the automation rule (this can then also be used in smart values to get…

Hi the branch "for subtasks" would refer to the subtasks of an issue. As the task was just created there are no subtask to "grab" for the branch. In order to create subtasks for the lately created issue use the branch "recently created issue". This would set the previously created issue in the context of "current issue"…

Hi @Lenka Burianova I guess your choice would be {{[date].plus[Unit]([number])}} * action: edit issue, field end date planned * update field with calculation of the smart value of your start date and add the smart value (number) of years See the documentation:…

Hi @Tim Foster , I can reproduce this behaviour by deleting the epic link in the parent. Are you sure that the task/story (whatever your parent is) is created withn the epic or does have "epic link" and was not linked to the epic by issue linking? Could you maybe show a screenshot of your issue? Best Stefan

Try to create an issue directly in the backlog and move it up to the "Board" list (see screenshot). 

exactly....I wanted to add this option with the "Issue Manager" too. Just realized i forgot that in my answer... Thanks for adding this information 

Hi @Martin , I was quite new to coding and jira automation too. Personally I started with reeeeaaally easy examples in jira automation, doing some examples from the community (like closing a story when all subtasks are done, transition a story to "in progress" when the first subtask moves to "in progress",...) After some…

Hi @kknoerr , could you please open the board settings and choose menu item "columns" and send a screenshot of your setting? Best Stefan

Hi @Thulasi Ram K , That is a very generous question and I´m afraid cannot be answered on point. What I can tell you is: * creating a project with new schema means that this special scheme is associated directly to this special project and as long as it is not associated to another project afterwards that´s the only place…

Hi @Kota Sreenivasa Shravana Kumar there is the functionality that special transactions in the jira workflow can be limited to several users/roles/groups but I cannot think of any time limit to set when this should be valid or not. From my personal point of view this even makes no sense. It´s more a question of your…

Awesome. Happy that it works =)

Hi @Bastian Schoell and welcome to the community. * as the trigger in this case is a version and not a common issue type the correct smart value is {{version.field/property}} * also please make sure to configure the scope of the rule (as there should be created in another project the rule need to be a multi project or…

Please also add thr screenshot of those issues from previous post (story and epic)