John Funk Community Champion

But why would using them be a problem? Just trying to understand, since they only limit further what they can already see. 

So why would you want to limit the quick filters access? 

No, but you can update the Default one to use the new things you intend for it. But I would copy that first in case you need it back. 

Hi Bartosz, Yes, if you are a Jira Admin, you can make that change for Company-managed projects in Jira Software, Jira Work Management, and Jira Service Management. Go to Project Settings then Permissions Click on the Actions button on the top right and select Use a different scheme. Then select the new one you have…

Hi Afahan, Only Jira Admins can create Company-managed projects. 

You update the security level field for the ticket to select the level you set up. 

Hi Paty - Welcome to the Atlassian Community! You should set the opsbar sequence in the transition property. See this previous post for guidance. https://community.atlassian.com/t5/Jira-questions/Opsbar-question-for-JIRA-cloud/qaq-p/960910

Hi Fabio, Create a custom number field first. Make sure it is available on the screen you are using. Then you can create an automation rule to populate the new field with the formula. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

Hi Seetham, You should always set your mandatory fields using the Field Configuration Scheme ofr the project in Jira. https://support.atlassian.com/jira-cloud-administration/docs/configure-a-field-configuration-scheme/

You can setup an automation to do that. Or you can manually update them as they are created. If you have one of them set as default - that will be what gets put on all tickets when they are created. 

I am not sure what you are asking then. What is the exact scenario?

Yes!!! :-)

No, you should add the project role in the same level. Each ticket can only be assigned to one level, so you need to be sure that each level has sufficient permissions for those that need to see those tickets. If you leave the Assignee one as is, No one but the assignee would be able to see it, and I don't think you want…

Haha - we have all done that I am sure. So select Current Assignee there for the one where only assignees can see it. And then you have to do another add to select Project Role and add Administrators.

Hi Olivier - Welcome to the Atlassian Community! You should click on the Give feedback button on the bottom left of the Jira Work Management project and let them know you would like to see the visual of the hierarchy. 

Hi Viktar, Try using some type of automation and using the field "initiator".

You should just have one Scheme with two different levels. Next, can you show a screen shot of the details of the level? 

Hi Mikhail - Welcome to the Atlassian Community! You will not be able to limit the fields using the standard clone feature. You can use an add-on like Deep Clone that can do that and call it from your post function. Or you can create an automation rule to create the new issue and populate the selected fields instead of…

So what is not working with what you have set up? Can you show some screenshots of your levels? And then what's not working with it?

Hi Angela, Security Levels is definitely the route to go. Create a level and choose Current Assignee. You should also add the Project Role for Administrator at the least so someone else can also see the ticket. Make the level the default so it will be added to all created tickets. Then the people will only be able to see…

Yes, I understand, but that doesn't get saved as a value anywhere that I am aware of. It only gets used to create the project with the same schemes as the existing project. So, again, there's not a way to know that. 

Happy Birthday @Kristján Geir Mathiesen !!! I was born December 15. @Sue Wilson - my wedding anniversary is December 17. :-)

Hi @Scott Paden Did you solve this? If not, can you give more details, like what you have tried? 

Hi @Drishti Maharaj - I would go ahead and contact Aha! support as they mention. 

Asegúrate de que tengan acceso al producto Jira Sofware en sus permisos.

Great!

No, you can't create templates at all. You can just create a project and get it all setup as you like, and then create other projects based on that existing project. 

I have been able to interact with Marketplace for the last 8 years. Thanks for the opportunities given to extend such an already great tool!

Hi Dylan, Yes, I would use a User Picker field for that. If you want to have multiple people in that field, use a User Picker (multiple users) type field.

Thanks for sharing that Jordyn. We actually use the External Fields add-on from Code forty-nine, but I have not done the search function before. I will have to give it a try!