Tim Kopperud Community Champion

Hi @Ryan Hamilton, You have an extra "." at the end in your expressions. Try {{issue.created.diff(issue.due date).days.abs}} TimK.

Hi @Princess Dagala, LinkedIssue cannot use IS operator. it need to be the = or != operators. See this document about supported operators for linkedIssue JQL functions | Jira Software Cloud | Atlassian Support Try this: created >= 2023-06-01 AND created <= 2023-12-31 AND project in ("IT Support") AND issuetype = Bug and…

Hi @Miroslav Šestak, you might find this document interesting using the webhook approach Webhooks (atlassian.com) Please regard this approach as advanced. I would again suggest you setup one or two test sites (Jira free or trial), to play around with when building this. Remember also to apply good and correct filtering on…

Hi @jonathan.wiebe, here is an example of a rule if it is Epic as parent you are looking for, and not parent of sub-tasks. Notice, as @Trudy P Claspill states in the comment, the brancing is Epic (parent) for this scenario. You don't need the filter Issue Type equals Epic after the branching, because only Epics will enter…

Hi @[deleted] , welcome to the community. This is a tricky question to answer because it fully dependend on the complexity of your current change and release management configuration in Jira Software. Change and relase management setup in JSW can often be rather complex if it have continually improved over the years in an…

Hi @Hashmi Muzzammil You will need to change the field renderer into Wiki style Renderer. * Go into Project settings, * select Fields in the left menu bar, * click on the "pen icon" (for edit) in the upper right part of the screen, * on your field select Renderers, * In the dropdown select Wiki Style Renderer, * press…

Hi @Brittany Montgomery, welcome to the Community. I suggest you apply IF-ELSE functions into your rule. For every IF clause you should configure the email according to that specific "IF thread". I have attached an image showing the principles for adding several IF-ELSE clauses. Notice the red circle, that means you need…

Hi @jonathan.wiebe Since you are saying "Trying to diagnose", I might suggest you add Log action entries into the rule. Then you can see exact where it goes wrong. The result will be shown in the audit log. See image below for examples. You must expect many "No actions performed" in the audit log, because any time an issue…

Hi @UdayKiran Not in the JQL in itself, but when a JQL is saved in a filter the filter can be configured to which columns (fields) to return. It is configured in the filter Columns setup. See image below. Are you using filter for search in the macro, like filter = "my filter", or have you written the the query wanted…

Hi @arno Sorry, since Create issue is not included in your version I don't think we have any way to solve this. If ScriptRunner isn't an option anymore I will mention the following as a possible, but unlikely, workaround: Earlier we could install the free SIL Engine SIL Engine for Power Suite | Atlassian Marketplace. But…

@arno, If you have the oppertunity, please attach an image of your automation Actions. It seems I cannot find what limitations affects the lite version. We might can configure the rule differently. (The supported version of Jira server ends February 2, 2024. When/If you upgrade to Data Center Automation for Jira full…

Hi @UdayKiran This depends on how you are using the macro. In the macro itself you will need to add the columns needed for fields "outside standard" to be shown. In the macro Insert JIRA Issue/Filter press Display options at the bottom of the macro dialog. There you can add columns to be displayed. If you are using a…

Hi @arno Do I understand it correctly that you have "Automation for Jira - server Lite"? The yellow IF filter in my image is the same as the orange JQL condition in your image, which is enabled. For Actions, is the Branch action disabled in your version? If it is enabled you have what's needed to build the same as in my…

Hi @Dearka Chan I see. Change the rule as shown below. You will need to find all issues created in this month and then use lookupIssues which will contain those issues. Then you can use the smart value function size to fetch this "counting number". Adjust the smart value formula to this:…

Hi @Dearka Chan You can du this with Automation and apply this to your custom field {{now.format("yyMMdd")}}{{issue.key.split("-").last}} Here is an example of such rule. Notice I used the Summary field, but you shuld change that to your customfield. The result will be like this: Edit: I now see that you don't want the…

Hi @arno You can solve this by using Atuomation. Below I have attached a rule that shows the principles on how to build this. The trigger and the filters you will need to adjust according to your need, because I don't have enough details to include any more in the example. . Try this, and if you have further question about…

Hi @Dennis de Laat welcome to the community. Boards are connected to the underlying filter permission. Limit the filter permissions so Viewers and Editors reflects only those who are allowed to see the board. TimK.

Hi @Brian Dobosz {{initiator.displayName}} will give you the person who did the change. Assigned by in your example. Timk.

Hi @Josef Sigl Sorry, this was a strange case. If... * the filter result image you attached with the columns in yellow are actually saved within the filter and not saved on My default or System * and other non-admin users sees the exact same result, including column setup, as you, when they executing the filter, ...I have…

Hi @Ardio Sam Yes, you can delete the issue from automation. If the original issue uses the same workflow as your Epic I might suggest you instead change the issue type using the Edit issue action. You don't need to create a new issue for this. Then you will keep all relevant history, even that it was nad when it was…

Hi @Ardio Sam You rule branches to Current issue, not All created issues. Se my image in the orginial answer. Current issue is always the issue that "flows" into the rule when it starts, and it will be that way during the whole rule execution. You therefore need to change the issue context away from current issue into the…

Can you attached an image of the gadget configuration? TimK

Hi @Josef Sigl Just a rough suggestion, since I don't know what fields you are requestion in your gadgets, or the exact filter setup. I do see that you have a "non-standard" column layout in the lower image which gives me a hunch. Filters can be saved with customized column output. Have you checked that the filter is not…

@serge calderara Yes, that is correct. TimK 

Hi @RG Only a Project administrator can remove Components. When a component is deleted, the issue still "live" normally, but without that component listed on it. Every filter query including this component will still work but the results will not include that component anymore. This means, based on your setup, e.g. a Board…

Hi @serge calderara You might try this. Step 1: * Create an automation rule triggered by Issue Created. * Add a filter to the rule where Issue Type = Sub-task (the actual subtask type you are using in your scenario). * Add the action Edit issue field. * Select the fields you want to set from the dropdown. * In each value…

Hi @Vidya Since you are using it daily you will not lose any data. The free plan is not a trial, it's for up to 10 users in production. I have had my free plan (for personal use) for years now, and no data lost. In this scenario regard the word "retension" about keeping "not used data" (e.g. backup, after inactivity…

Hi @Greg Weber Jira first search for issue key in the subject field, if not found it will inspect the mail header (simplified). For exact details see this link How JIRA Updates Issues from Email | Jira | Atlassian Documentation TimK.

@Miroslav Šestak, I also suggest you set up a free Jira site or a trial site, if you dont want to concern your partner with the setup before you have everything up and running. This applies to mail setup as well as webhook configurations. Then you can test between your site and the new "fake partner" site. TimK.

Hi @Miroslav Šestak You might have a look at this Replying to email notifications from the automation rule to be added as comments to existing issues | Jira | Atlassian Documentation If you can involve your partner I would instead use webhooks. Principles explained here: * Have the initiating rule on your side as described…