Comments
-
Hi @Jan Walsh , you are right, the editor is removing the parentheses. I've found out there have been issues with this behaviour in the past. But, it works for me, even without the parentheses. So, you are saying, that if you create three filters * type = Task * type = Feature and status = "Ready to dev" * type = Task…
-
Hi @Michael Gardiner , when you edit the automation rule, in the Rule details there's field Notify on error - you can select "Don't notify" there. But this means, you won't be notified, even though your rule fails "normally", not only after these bulk changes. Maybe there's a way for you to optimize/change the rules…
-
Hi @Sandee Devine , welcome to the Atlassian community! Please, see this article. Thank you.
-
You can check the workflow, whether there are some suspicious post functions/conditions/validators, but you will probably need Atlassian to provide you with more information.
-
Hi @Steven_Doherty , as this is Jira cloud, there is not much you can do to investigate the problem more. Are you on a paid plan? It is possible for you to contact Atlassian support directly?
-
Hi @Jan Walsh , welcome to the Atlassian community. Please use parentheses like this: type = Task OR (type = Feature AND status = "Ready to dev")
-
@Mykenna Cepek When you want to add permission to some permission scheme, you can select item "Application access" and there is select field with the options I mentioned before. So, I'm saying that "applicationRole" with no additional parameters means "Any logged in user" = user with any license (both JSM agents and JSW…
-
Hi @Anna Oaks , no, please don't share your password with anyone. They need to create their own account with their password based on the e-mail address you've shared your board with.
-
Hi @Mykenna Cepek , permission can be granted to Application access - there are options * Any logged in user * Jira Service Management * Jira Software In your case applicationRole = Any logged in user as there are no additional parameters
-
As I'm still partly on a parental leave and work mostly during the evenings, I'm usually going at it solo. I have to be very effective and fast as I don't have much time, so I see me more as a sprinter.
-
As I'm still partly on a parental leave and work mostly during the evenings, when others are resting, I see us as relay runners. When one ends, the other starts :-).
-
This week I've thanked my colleagues with this post. A lot of of them are Jira Admins, so I hope it also counts a little :-).
-
Thank you for a fun activity. Here's mine.
-
Hi @Daria Kulikova_GitProtect_io , thank you. I'm always happy to hear from somebody, who loves their job. Best wishes in the future!
-
Hi @Vronik , thank you, yes I totally agree, I'm very lucky.
-
Hi @Susan Waldrip , thank you! I hope it will help somebody.
-
Hi @Andy Gladstone , you are very kind, thank you very much!
-
Hi @John Funk , yes, you are right, I remember I was pregnant back then. Sadly I wasn't able to publish my review, because Amazon allowed this only for their customers.
-
Hi @Rafael Garcia Tamarit , thank you!
-
Thank you, very helpful!
-
Welcome @Ncumisa Veronica Booi !
-
@Monique vdB So, I tried and published two new articles and one discussion. Nothing :-(. Level 10 is unreachable for me :-(. Anyway, thanks for the update.
-
Hi @Daniel Cottrell , I believe it is connected to this announcement. I've also received these emails.
-
Love this!
-
Nice!
-
Congratulations!
-
Hi @Dave LIAO , our use case is very complex. We have two large Jira instances with hundreds of projects and thousands of users. There are many apps and a lot of custom development too. From the analysis we already know it will be very problematic and this also means expensive. This is the reason we are trying to get in…
-
Hi @Dave LIAO , thank you. We are migrating data from one Jira to the other existing Jira.
-
Thank you, @A A Ron Geister _Trundl_
-
Hi @Luzmarie Ramirez , if I answered all your questions, please mark my anwer as accepted, so that it can help others in the future. Thank you.