Arkadiusz Inglot Specialist

Ive created a ticket before this article. Indeed, seems to be a bug: Hello Arkadiusz, Thank you for your candid feedback and for clarifying the urgency of this situation. I completely understand your point Update on Investigation: Internal Incident Raised I want to inform you that we have received similar reports from…

Thank you for your message! That gives me a hope, that its more related to some sort of bug rather than a change.

There are 3 elements where u can iterate though objects. They are different but sometimes can be abused to achieve the goal. 1. Branch 2. Lookup issues (blue action) 3. Scheduled trigger (green trigger) You can consider rebuilding your mechanism to get "recently created issues" (or list of keys to be linked)) using…

Will Atlassian provide auto-update for all the automation rules that uses smart values like {{issue.reporter.displayname}} in all automation components? :D Untill that I'd stick with "issue"

Hello @Clayton Fortunately I have some semi-automated migrations done so far, thus: * Before you migrate, on site you are migrating from:* Review your Custom Fields* Delete all unused or mark them in description - put there a string, which will be easy to search for on new instance. * Eliminate duplicated names - resolve…

Hi, You can use plenty of functions to extract the string. The ideal would be to create your issue using custom fields and providing specified value inside - even using API if needed. To make it simpler I'd first split it by \n and then extract the value starting with some string: You can try:…

Hi, Please navigate to Rule details, and make sure: Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule. is checked. This allows a automation rule trigger another rule.

Go, go! Great idea!

Hi, I see two another solutions which may be helpful: A) Create hidden custom fields and put there your status names: https://confluence.atlassian.com/jirakb/how-to-transition-to-the-previous-status-of-an-issue-using-automation-rules-in-jira-1236599919.html B) Depending on complexity of your workflow you can rename all…

@hpatani I did not test it yet, but saw in marketplace; https://stsbetsys.atlassian.net/jira/marketplace/discover/app/com.gebsun.plugins.jira.defaultvalues

Hi, * Out of the box Jira: * You can tryhard and achieve that, but personally I do not recommend below solution. * As you are unable to customize/modify system's Description built-in field, you can create another custom field named "Advanced description" and add there a default value. * Notice 1:* Please keep in mind that…

Hello Please keep in mind, issues are part of a project (technically speaking) not part of boards. boards are just a visual representation of some JQL filter which allows you to see issues devided on columns (statuses). It means you need to double check the board filter why it is not displaying such cloned issue. 

Hello I would love to see there a "date picker" or "date time picker" field types! Best!

Hello Please select proper trigger for your automation and then edit you summary with new 'semi statgic' value. In that case You can handle both cases (issue create + update) using different trigger: * Field value changed* Field: Presenters * Change type: Any changes * Create issue + Edit issue * Edit issue:* Field:…

Hi. There is no way to limit rule execution base on issue type. You can run it everytime and limit it by "if block" statement. Issue fields condition: * Field: issue type * Condition: Equals * Value: Story

Found source of issue: After forcing error on purpose Branching displays the JQL which looks like this: ABC-617: "((project = ABC and issuetype~'Asset' and 'Service Tag (serial number)' ~ \"Z6789X276\") AND (key != ABC-617)) AND (project in (10045))" - The operator '~' is not supported by the 'issuetype' field. Dont mind…

In addition: This works in Navigator & Branching: project = ABC and issuetype='Asset' and 'Service Tag (serial number)' ~ \"9283MGL5\" This works only in Navigator (not in Branching): project = ABC and issuetype='Asset' and 'Service Tag (serial number)' ~ \"6789G2\" No spaces, no white chars, no any special chars. Why?

Hello, let me give you some hints: * Automation rule A or workflow post function to edit a field value.* Issue transition trigger TO status. * Set proper timestamp (today+7d) to non editable custom field. * Automation B* Scheduled run every day at 8am (or other time) * If custom field value (with timestamp value) = today…

Hello 1. What is more important in this case? Onboarding or Reporter (user X) to set the values in your problematic case? 2. Create one rule and make proper if statements. Ths below is an example and you should set IFs which suits you properly, as both triggers which you described (1, 2) do not exclude eachother.

Hello It can be quite complicated, but I have no other solution for that. This may not be a optimal way. Assumptions: * Your main task X is issuetype=Task * New Custom Field named: "startIndex" (number field) * Via manual automation (or any other trigger) you create 3 subtasks (issueType=Sub-task) linked to main task - I…

Hello as well a predefined list of (non-ASAP) outgoing and incoming dependencies between them. What exactly do You mean by that? 1. What the dependencied are exactly in terms of jira objects? 2. What are Incoming and outgoing ones? (linked issues with specific relations?)

Its 07.08.2023 and my automation still has: Each Key will return its corresponding Value. The Value that you define here can be a constant or a smart value. You can add up to 20 entries. How to force an update for my instance so we can have limit of 200 records fot that?

Hi In automation: Edit issue action > field called: "Flagged" > select your created values

What exactly do you mean by: "because the issue fields did not capture everything I wanted."? We are also using project for HR, and we were able to use all the fields as our HR needed to provide them all the data. Maybe we can help you there?

What if you use: {{issue.description.substringAfterLast("*(color:#BE")}} or simillar approache?

For me it is working that way: 1. Edit description {{issue.description.remove("This is the first line.")}} 2. Refetch data 3. Edit description once again {{issue.description.remove("This is the last line.")}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/

@Pradeep CheekurthiBut initially the guy is asking about creating a SPECIFIED ISSUE TYPE ticket instead of any "issue type in project".

You have not specified a trigger for that rule. In addition - you would like to add IF STATEMENT before "For loop" that checs if current status is the only one you want move back from. Just to make sure that automation will always go one status back instead of infinity. Combain it with proper workflow. Just type…