Vishal Biyani Expert

@Bill Sheboy Could you suggest why the rule is not working in Martin's instance while it is working in my cloud instance?

Can you share your automation rule screen shot? you should be able to specify an if condition to not send the update to slack channel, if for the field name matches for which you don't need/want to send the update for.

@Seu Jye Ying When you reach your user license limit in Jira, you can still create new user accounts; however, these new users won't have the 'JIRA Users' global permission, preventing them from logging into your Jira instance. To address this, you have two options: Upgrade Your License: Increase your current Jira license…

@Aleena Run a JQL like in search parentEpic = <Epic Key> Then Click on Bulk Change all Issues. Map Epic and Standard Issue Types to new project. In the next screen, it will ask to map the subtasks to new project. If you want to change the issuetype of subtask you can do that. See if this works for you

@Piotr Koćwin You can use triggers like Manual or Scheduled instead of say tracking Create Issue event as a trigger. Will that work for you?

Can you resend the invite to user?

@Amulya Sankara in your sprint board view, what is the statuses mapped to right most column? if you remove your custom statues from right most column, I believe, you should be able to achieve your use case when closing the sprint. Issues with these statuses will be moved to next sprint. Check and let me know if this works…

I again ran my automation my audit log shows match when 1st fixVersion is added. There seems to be a case mismatch in fixversions. Can you use fixVersions and try with that? Additionally, do below when creating smart Variable, in smart Value, put like this {{#debug}}{{issue.fixVersions.size}}{{/}} It will print the value…

@Marc Hendrik Herdina To check usage you need to go to https://admin.atlassian.com Products The page opens in that page, in left navigation panel, under site and Products, you will see your site. Click on that and then click on Storage

@Pengshan Dai What do you expect by making rule clickable? How would it be used in automation flow?

Can you elaborate with an example as to how you would like to see the status updated in custom field? Do you plan to use one custom field or multiple (1 each for Epic, Standard Issue, Subtask)? Let's say you have 1 WP. Under it 4 Epics. Each Epic has 2 to 4 Standard Issues. Each Standard Issue has say 3 to 4 subtasks. Once…

@Ahbosch When you need to update subtask summary, use {{triggerIssue.parent.parent.key}} - {{triggerIssue.summary}} When you need to update standard issue summary, use {{triggerIssue.parent.key}} - {{triggerIssue.summary}} See sample automation that i created for your understanding. I used manual trigger, you can have the…

Your hierarchy is WP -> Epic -> Standard Issue Type -> sub-tasks * One WP can have multiple Epics. * One Epic can have multiple Standard Issue Type. If I understand it correctly, in your WP, you want to see the status of all related Epics/Standard issues etc. Are you on premium subscription? if yes, you can check plans, if…

@Emilio Valdivieso Can you elaborate on the business problem you are trying to solve with an example? what do you mean by Work Package? is it a standard issue type linked to Epic or a subtask issue type?

@Hitarth Bhalla To resolve this error, you will need to map the custom field on the screen. Since custom field numbering can be different for different project, you will have to check with field names that you are mapping to identify the custom field name in jira.

@_string_ if you don't have script runner, then the only option is to have multiple workflows and based on the custom field value, go to that workflow. Refer to below article

@chamali Haveesha Try with and it will work for you. The asNumber forces JIRA to treat the value as number {{triggerIssue.order number.asNumber.format("00.00")}}

@Shamima Essop Is this a company managed or team managed project?

@Carlo Maggioni Go to https://admin.atlassian.com Click on Directory Click on Users on the left side panel. After that you should be able to activate the user

can you just add one more log statement and show what value is coming in {{issue.customfield_19832}} ?

Can you create the variable before the if block When i try like this, it is entering the if block when first fixVersion is added

@Maurice B. You are using Scheduled as a trigger. Therefore, triggerIssue will not come into play, in my opinion. For Lookup issues is your JQL something like below: project = XYZ and issuetype in standardIssueTypes() and issuetype not in (Epic, Initiative) and parent is not Empty This will return all standard issuetypes…

Can you share the automation rule that you have so far? if you use advanced branching, you should be able to loop through all comments. But would be good to see your rule built so far

@Martin Karlsson {{issue.fixVersions.size}}can given the number of fixVersions present on the issue if 1 a new fixVersion is added. if > 1 then more than one fixVersion if 0 then all fixVersion is removed From documentation, looks like below may not work for list of fixVersions {{fieldChange.fromString}}

@Jesús Velarde Can you elaborate a bit more? Are you using REST APIs or automation? if you are using REST APIs what are the end points that you have used

as the lookup is not working, need to see what is the value that is coming in automation for issue.customfield_19832 Log an action using {{issue.customfield_19832}}

@amar amarendra Did you follow migration checks and processes defined by Atlassian? if you have migrated the data from one db to another, then it is likely you will face the issue that you are talking about, Migrating Jira applications to another server | Administering Jira applications Data Center 10.4 | Atlassian…

@marianna_taborda In JIRA cloud, you should be able to extend the view by dragging the horizontal bar. Are you not able to do that?

@surya Have you verified your access permissions to the project?

Glad to know this worked for you.