Daniel Ebers Expert

Sure, you're welcome. It was really something to learn and to try. If I understood everything correctly Dirk will present an alternative solution in here: https://community.atlassian.com/t5/Jira-questions/How-to-make-a-OR-condition-in-Jira-Automation/qaq-p/1587067 You will have to check which one suits better. For your…

Testing in cloud instance I can recognize it is calculated for a specific status in total (a simple addition of time spent, no matter how often the issue was in a particular state).

I believe the question is how the number are evaluated - or in other words, why there is specifically the counts appear in those categories, is this correct? There has been a dicussion on that, which probably helps:…

@Emanuel Boderat the end of the trial period the plan falls into "Free" if you do not supply billing information (credit card data).

Could you please check using "Permission Helper" from Admin Helper what it is reporting back?

I tested a bit further - and should prepend the tests were on Jira Cloud I could repeat on Jira Server. These queries work - which means they exclude the single date, here, December 7th 2020: project = DEMO AND (updatedDate < 2020-12-07 OR updatedDate > 2020-12-08) ORDER BY updated DESC project = DEMO AND (updatedDate <…

It is getting a bit complicated I must admit :) But for the moment I believe the problem could be in first rule we are transitioning to status "Completed" but in second rule we are listening for status "Done". So the second rule would have to start with "When: Issue transitioned TO Completed" :) If this also does not work…

Could you please show the complete setup of both rules (= like in the last screenshot - just for both rules)?

Hi @Soporte Sine95 using this query: project = DEMO AND (updatedDate < 2021-01-10 OR updatedDate > 2021-01-11) I was able to filter out January 10th 2021 - could you please double check if it works for you? Cheers, Daniel

I see, but in this place they are needed to do the automation. Otherwise parts would be missing to be executed - at least in this architecture of the rule. As for the second question - yes, the rule in the "SD" project must be checked for allowing to be called from other rule - here specifically in order it can be executed…

Could you double check if you have (edit) permissions for "HW-Discription" project's underlying filter ("Filter for HD board")? From what I understood you need permissions there. For my case the filter is there and shared with "HELPDESK, All Roles" You can share with: * Groups * Projects * or: Any logged-in user As a site…

To my knowledge there is no such distinction. Why do you consider this important to your use case?

Then there are not much options. You could reach out to Atlassian Billing Support - like roughly stated here: https://community.atlassian.com/t5/Atlassian-Access-questions/Only-Org-Admin-left-the-company-and-does-not-cooperate/qaq-p/1473585 If this won't work out it is a lost case as you won't get back to Org Admin.

When navigating to "Board Settings" -> "General" -> "Shares" you should be able to see the part "Shares". In case you cannot see it please share how it looks for you. Please kindly be reminded, it is a classic board.

Yes, the first rule is with SWH project. It says: when the issue is transitioned to done it will check for any issues with link type "is demanded by". A finding will be transitioned to "done". Then the second rule (in "SD" project") catches. This one says: as soon as an issue is transitioned to done (coming from first…

Yes, it also works without labels - here is what I can come up with, using two rules. For "SHW" project: For "SD" project: In a test, it worked very well. Please note, for the second rule the checkbox "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to…

I would also be highly interested what is visible from "History" tab of a specific issue. When the user's name is appearing in an auto-generated mail one must assume that the user name was set as assignee as the time the mail was sent. After that seeing assignee as empty must basically mean "something" changed the…

I have been facing a very similar issue, but this time Jira <-> PostgreSQL, basically like described in: https://jira.atlassian.com/browse/JRASERVER-66178 While I could not find anything for Confluence on jira.atlassian.com it still could apply to Confluence in some sense. Of course, a pretty complex password which cannot…

Hi @Jessica Ren this has been asked a few times here in Atlassian Community (just one example here) but there is no intention to generally change the current behaviour. What means: if you want to see the Sub-Tasks you would have to include them into board's filters - but there is an option. In…

When you can rule out some other colleagues previously executed backup you can still raise this request with Atlassian Support. From Community it is hard to tell why the button is greyed out - more than that, there are no logs you (and/or Community members) could have a look into.

There used to be some options - but they focus on Server rather on Cloud (for example the HTML macro). For Confluence Cloud there are Apps from Marketplace - you could review them if they suit your needs. Here is just one example:…

That sounds more like a refreshing/timing issue. The statement "you can't view this issue" usually says for sure the issue is already deleted. Maybe it needs some seconds for the queue to update and to show the current situation - we even could observe this for other automation rules. Is there any timeframe until you see…

You could add the user account to the notification schemes of the projects you want to see the updates about. But I am sure this would cause a mail flood if you "subscribe" to any event that happens in a project - maybe a selection for "Issue Created", "Issue Commented" or "Issue Resolved" will be needed to see through the…

While this sounds more like an organizational consideration where I do not want to say much about I can at least confirm you would need to hold Jira Administrator permissions in order being able to create a custom field. An automation rule, however you can create by holding Project Administrator permissions - you do not…

Sure, you're welcome. Glad that it is working now!

And is this not the same thing as in https://community.atlassian.com/t5/Jira-questions/How-to-make-a-OR-condition-in-Jira-Automation/qaq-p/1587067 ?

Assuming the rule is already there you could go to "All Rules" and change the scope. In global rules it cannot be this time as the scope is not yet set to anything it would qualify it "global".

Hi @serge calderara one approach would be to have two rules like the following: For project SHW: For project SD: To summarize: As soon as in project SHW an issue is transitioned to done in it's linked issues of type "is demanded by" a label is set. The rule for project SD listens for the appearance of label "Notify". As…

Actually, it works pretty well. In global administration you need to add the projects by widening the scope to "Multiple projects" like shown in the screenshot above - then things should really start to work ;) Note: you need to be Jira-Administrator to do it - it won't suffice holding project administrator permissions.

I see, there was some minor tweaking still needed: Please notice the rule was executed successfuly earliest when put global automation, and there specifically with Scope "Multiple projects" like shown in the screenshot. Please note that you can still use "When Issue assigned" instead of "When Issue commented" as well as…