John Funk Community Champion

Definitely peaches for me. And now is the perfect time for those in the US. Just had one last night and more today. :-) Also, so cooked peaches in a light sugary sauce with cinnamon served warm over vanilla ice cream. YESSSSSSSS!!!!!

Agreed!

No result? Or was there an error? And is it the same error that you get if you try to do the opposite? 

Hi Vanessa - How is the JSW issue getting created? Is it being cloned by the JSM ticket? Is it manually being created? 

Did you try to add the group to the User instead of the user to the group?

Hi @Ilidio Faria - See common use case number 1 in this guidance: https://www.atlassian.com/software/jira/guides/expand-jira/automation-use-cases

I would implement Issue Level Security with a default security level that does not let any vendors see the issue. Then I would create a security level for each vendor and add the ability of that particular vendor do see the issues. You can see more about how to implement Issue Level Security here:…

What if you just edit the user and add the group to him, instead of editing the group and adding him to the group?

Hi Nacho - In Jira Cloud there is a condition called Sub-Task Blocking Condition that you can apply to the transition to Done. I would suggest you add that. 

Are you sure you also have Site Admin permissions? Can you describe the exact steps you are doing? 

Hi @Codafi - Welcome to the Atlassian Community! The ability to have multiple workflows with different issue types for Team-managed projects is not available yet. It's "in the works" right now, but I don't know the timeline. You can follow along with the product roadmap…

You are welcome. :-) That's a big part of what Community is here for, so bring your questions!

언어 번역으로 인해 용어에 약간의 차이가있을 수 있지만 감시자 관리 권한을 찾고 있습니다. 권한 체계에는 유권자 및 감시자 권한이라는 섹션이 있습니다. 해당 섹션 아래에 필요한 권한이 있습니다.

Hi Helen - Welcome to the Atlassian Community! I am afraid that you would have to setup a separate Issue Type for those issues. Then you can control which fields appear on a screen by Issue Type. But there is no field level security within Jira that would allow you to do it otherwise. 

I would ask them to provide the source of their information. This is THE roadmap tool for the product, so I don't know how they decommission it. But I also don't work for Atlassian. :-)

Hello and Welcome, Christopher! We are glad you are here!!

Hi Tasha - Welcome to the Atlassian Community! Yes, the code you have there should do the trick. :-)

Can you share a screenshot of the actual rule? Along with the Audit Log that shows it is not working?

Ah, you are using a Team-managed project. Click on Features and then toggle on the value for Releases. 

project = "Project name" AND "Approver[User Picker (single user)]" = currentUser() AND "Approver 1[User Picker (single user)]" = currentUser() AND "Approver 2[User Picker (single user)]" = currentUser() AND "Approver 3[User Picker (single user)]" = currentUser() AND "Approver 4[User Picker (single user)]" =…

If they vendor can see all of the issues in a single project, then you can handle that with the Permission Scheme - only grant that permission to the vendor/user. If they can see some issues on the project but not other issues, then you will have to do that with Issue Level Security. But you can't just set the security…

Hi John - Welcome to the Atlassian Community! Yes, screenshots would be helpful. 

Hi @[deleted] That would seem unlikely to me since this is a revamped product from the old Portfolio product. Are you hearing this from Atlassian employees? 

Can you share screenshots of the actual rules? 

Can you list the exact parameters that are not working? 

I was born in the US as was my parents and grandparents, but not sure much after that. I have heard our heritage is German on my father's side and Scottish on my mother's side. But not sure have many generations back you have to go for that. 

Agreed

No, JIra Administrator and Jira Site Admin permissions are all separate from Project Permissions. You can be a Jira Administrator and have the ability to change all settings for the entire instance, but not have permissions to even see a project if you don't have Browse Project permission in that project's permission…

Hi Patrick - Welcome to the Atlassian Community! Go to Project Settings > Apps > Project Automation

Hi Pranav - Welcome to the Atlassian Community! Are you trying to do that through the API? Are you sure that you have Jira Site Administrator permissions in the User Management section?