Sebastian Krzewiński Community Champion

Hi @zhangqian04 Did you try something like this: {{issue.customfield_10015.diff(issue.customfield_10016).toBusinessDay()}} All helpfulinformations you can find here: - https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/#calculating-the-difference-between-two-dates (see…

Hi @Dana Davies I think there isn't domething like execution order. Both automation mechanisms based on JIRA events and it process events as they "catch" them in order first in, first out. Second thing - how time consuming are your rules. If it took a quite long time, less time consuming rules triggered after time…

Hi @orit.vivante Did you check atlassian-jira-security.log? (https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html) Regards, Seba

Hi @aliang Watchers field is connected with permission View Voters and Watchers. If your user has this permission watchers field should be visible on issue view. Regards, Sebastian

Hi @Jack Brickey Thanks for reply and explanation.

Hi What url you have in your request? Seba

Hi @Guy Walker It look like you add wrong issue type name or id. Please list all issue types and check if you use correct name or id (<JIRA_url>/rest/api/2/issuetype) Regards, Seba

Unfortunately no but I would try make config very similar as for JIRA/Confluence/Bitbucket.

Hi @Marco I'm not sure that with embeded automation you will achieve this. Please try Automation for JIRA Cloud Lite ( link ). There you can find a lot more ways to do this. Regards, Seba

Hi @Joshua Rasbash Yes, you can have different licenses for each app. If you want manage all users by crowd you must remember (and you mention this) that crowd must have license such as the biggest of one of your apps. In crowd you can create several applications that will serve specific users to applications or you can…

Hi @James Brown Did you check this doc - https://confluence.atlassian.com/bamboo0515/monitoring-and-profiling-bamboo-894238190.html ? Regards, Seba

Yes, it is still unavailable

Hi In Epic link field JIRA store Epic's issue key not epic name. JIRA only display on view issue epic name. You can check it browse issue via REST API. Seba

Hi @Michael Rabold Yes you can. You have two ways to achieve this: 1. You can set field as required in field configuration (field will be required all time) - link 2. You can add validator to set field required on workflow transition (field will be required only on certain transition) Regards, Seba

Hi @Chirag Epic link field is set in issues added to certain Epic issues. Epic name field is set only in Epic issues. Example: You have issues like this: * Epic 1 (ABC-1)* Issue in Epic 1 (ABC-2) * Epic 2 (ABC-3)* issue in Epic 2 (ABC-4) * issue in Epic 2 (ABC-5) When you filter issues: - Issues ABC-1 and ABC-3 have set…

Hi @Matt As I remember if you want move your script to files (IMHO this is a very good idea) you should put it in home directory. More information you can find in other community posts: - https://community.atlassian.com/t5/Adaptavist-questions/Need-to-know-the-file-path-in-server-level-where-the-Script/qaq-p/728856 -…

Hi @Chris Harney How look your application access page? Seba

Hi Did you try {{issue.comments.size}}? More info you can find here: https://docs.automationforjira.com/reference/smart-values.html#issue-comments Below example how you can use it: Regards, Seba

Hi @Sarath My configuration block summary field on edit screen. Behaviours works only on create and edit screens so you can't achieve described action (block inline edit on view screen).

Hi @Sarath Check this: In my example I used summary field but you can change it to Story Points. I marked field as read only and set negative condition wich allows users from group jira-administrators to edit summary field. I hope that this will help you :) Regards, Seba

Hi @Shawn B. Think about "project" in JIRA as a set of configuration defining this project and storage for issues from this project. In every project you can define issue types (Service Request, Incident, etc.). For every issue type you can: - define set of fields that will be appear when user will choose proper issue type…

I also got this error but it works. Did you run it? If it not working please change it a little bit import com.atlassian.jira.component.ComponentAccessor def cField = ComponentAccessor.customFieldManager.getCustomFieldObjectByName("<user picker field name>") def cFieldValue = issue.getCustomFieldValue(cField).name…

Sorry that my answer wasn't clear enough. 1. Workflow should look like this: 2. On create transition you add fast-track transition post function (without any condition) 3. On loop transition you add your subtask creation function The reason that I do cases like this was because I saw that on create transition issue isn't…

Hi @Bunty Try this: import com.atlassian.jira.component.ComponentAccessor def cField = ComponentAccessor.customFieldManager.getCustomFieldObjectByName("<user picker field name>") def cFieldValue = issue.getCustomFieldValue(cField) if(cFieldValue.name == null) { issue.setAssigneeId('username') } if(issue.assignee==null) {…

In cases like yours I make a "loop transition" and fire it usting fast-track transition. In your case it will be loop from Todo to Todo. Then move Create subtask post function to loop transition. On Create transition add fast-track transition post function and mark that loop transitionn will be triggered without any…

Hi @Liam Maeder What do you use to do this? Automation for JIRA add-on perhaps? Regards, Seba

Which one you run in console and it works? Can you describe where you put your post function?

Hi @Luvo Kautah Ncibane Please check this code and modify it if something will be wrong. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink def condition=false //def inwardLinkedIssues = ComponentAccessor.issueLinkManager.getInwardLinks(issue.id).each{ def…

Hi @Jai_Nirwan I have simillar case like you. Make sure that: - you choose correct workflow in Guide workflow - you put your code in server-side script in customfield_10500 section. IMHO I will change your code a little bit and move first condition and use built-in conditions in Behaviours. Take a look on my…

Sure :) Please paste link to new topic.