Tim Kopperud Community Champion

Hi @Varunish Garg , welcome to Atlassian Community.

Great, I'm glad it resolved the question. TimK

Hi @mateus.oliveira, welcome to Atlassian Community. Just an idea first. If an app from the market place is an alternative option you could solve this rather elegantly by creating a drop down which dynamically lists only free days or spots. So, if in example you have 10 issues booked for a certain date, and 10 is the max…

Great. Glad it works. TimK.

Hi @Christian Fischer, you can use the Log action to simulate an "empty action", though I don't think you will solve the actual problem here. Instead of branching I might suggest you us a filter, something like this TimK.

Hi @gaetano.ricchetti, welcome to Atlassian Community. I not fully sure I understand your question correctly, but if with "AKA words" you mean "also known as" and you want to show the definition of a specific word or an abbrivation, I will try to answer. With the new Atlassian AI implementation you can double click any…

Hi @Avrohom Yisroel Silver, if I understand your question correctly you should be able to simply press the minus key "-" to collapse all or expand all, ref: Press question mark "?" to display all available keyboard shortcusts. TimK

Hi @nagarajan.b, welcome to Atlassian Community. Just so I understand this question correctly, I'll need some more information to be able to assist better: * Where do you want such a signature to be inserted?* In the description field when you create a new Jira Issue? * On every comment you post on an existing Jira issue?…

Hi @Tara Bell , I think the reply by @Ste Wright is the correct answer to the problem you experience regarding fields not showing. TimK.

Hi @Tara Bell, if I understand your question correctly, when configuring the issue screen it have a section dedicated to hide empty fields. Drag&drop those fields above this section devider. In the image below you see an example of the fields Sprint and Fix versions are hidden if empty (notice the divider). Below I have…

Hi @Azandè Caldicott, I see (ref. lower left corner) that the project Test_Scrum is a Team Managed project. Such project type doesn't support swimlanes. You might vote for support of this feature here. I suggest you create a new project (e.g. Test_Scrum2) as a Company Managed project. Follow the wizard for the Scrum…

Hi @Azandè Caldicott, if I understand yor question correctly you can do the following. In your Scrum board press the Elipsis menu on the upper right and select Configure board. Under Settings select Swimlanes and in the dropdown select Epics. This should give you a view like this on your scrum board. TimK.

Hi @IT Support, by looking at your attached image it seems you are using legacy automation. This version of automation was promoted by Atlassian before they purchased Automation for Jira from Codebarrel. Now Atlassian has swithed to a new automation engine, and the one you use is regarded as legacy as you see from this…

Hi @IT Support can you attach an image of your rule action where you try to set the summary using smart values? TimK.

Hi @IT Support, you might use Automation and create a rule like this: Replace the filter (If) to your needs, so only relevant issues are affected. Use smart values to rephrase the Summary field by using something like this: {{priority.name}} - {{summary}} The result will then be like this: TimK

Hi @Martina, you might add an automation rule triggered by schedule and define a JQL for the due period needed, e.g., like this: The JQL will be like this due > endOfDay(1) and due < startOfDay(3) TimK.

Hi @Devin Holland, I think the rule can be simplified. You might try something like this: With the JQL (created > startOfDay() and created < startOfDay("8h")) OR (created > endOfDay("-8") and created < endOfDay()) TimK.

Hi @Devin Holland, welcome to Atlassian Community. Yes Jira can check for specific time, though when specifying it by exact time you will need to add the date as well, as in syntax specs for searching date fields Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd' Based on your search…

Hi @Sandesh TM , then the rule will be like this, very similar TimK.

Hi @Sandesh TM, I might suggest you use automation for this and create a rule triggered by Issue linked, like this example: The problem you experience is discussed in the comments here. The issue is marked resolved from Atlassian as it did implement a linked issues event, though it didn't add feature for notification. You…

Hi @Gonzalo Perez Alonso, sorry but it seems I was wrong regarding the field doesn't need to be included on the screen. The field need to be on the screen associated with the action. Can you confirm the field is associated with the Edit screen? EDIT Hi @Gonzalo Perez Alonso, great. Good you got it working. TimK.

Hi @Uldis Berzins OK, good. Then we can conclude the rule is firing only once as wanted but the rule do edit the issue twice which is not wanted. I suspect the root cause is the rule itself. Can you add log actions into your rule, so we can see where it hits in the rules Audit log? E.g like I have done here: TimK.

Hi @Sergio M. Gard , did you try the last JQL I sent in my prevous comment? This should fetch the issues. Key is the identifyer for the issue, so the issue numbers you are reffering to are the keys. They are the same. On every issue you will se the key on the top, like shown here: Those works in filters when using "key in"…

Hi @Sergio M. Gard, in e.g. MP-1035 (your first entry) is the project key MP or is it actually MP-1035? I mean are MP-1035 actually an issue key, and not the project key? If you are actually refering to issue keys in your JQL you will instead need something like this: key IN (MP-1035, MP-1244, MP-506, PCT-8396, PCT-10026,…

Hi @Gonzalo Perez Alonso, since you have now adjusted existing status properties I might suggest that you start without any permission properties at all. Instead of true for jira.issue.editable, you can delete it. It's easier to start out simpler, and add feature in the next step. Have you also confirmed that the rule…

@THIBAULT JOSSELIN, great. Looking forward to hear from you. TimK.

Hi @Uldis Berzins, thanks for attaching in image of the rule, this is helpfull. Though I understand you get two different results let's first focus on the "rule executes twice". Issue history only shows that the issue was editet twice, it doesn't actually show the number of rule executions. The rule audit log will show if…

Hi @Sergio M. Gard, welcome to Atlassian Community. If I understand your question correctly you might create a filter listing all projects needed for your result set by using IN like this: project IN (projectA, projectB, projectC) Then you can manually add or remove any project key according to the current involvment. In…

Hi @Uldis Berzins, one reason for this can be that you have another rule triggering this rule. Check if the rule is allowed to be triggered from other rules by looking into the Rule details. Try to temporarly uncheck Allow rule trigger if it's cheched and test if it now fire twice. TimK.

Hi @Craig_Harley, glad I could be of help and that the error is gone. Just inform me here if you need further assistance with a way to return rows from the query. The formula suggested might need a little tuning to return records from your real data set. TimK.