John Funk Community Champion

Hi Jacob, Make sure the Security Level field is on the Edit and Create screens used by the projects. 

Hi @igefa IT-Service To be honest this could be a rabbit hole of chasing things. I would go ahead and open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

Ah that may be! I have not tried any JPD projects yet.

Hi George - Welcome to the Atlassian Community! Create an Organization then add the user to that Organization. Then add the Organization to all tickets the the user should see.

No, there isn't. 

Hi Vincent, If you are using a Company-managed project then it is already there and ready to be used by Jira Software. Just go to Project Settings for the Jira Software project, click on Summary and then on the Workflow Scheme name. Then click the Switch Scheme button. Finally, select the workflow scheme that was attached…

Hi Muhammad, Take a look at the Revyz Backup and Restore app on the Atlassian Marketplace.

@Matthew Canham 

Hi Amy, Possibly, but you will need to try it out. Make sure they are in the Service Desk Team project role for the one they need to be an Agent for and just the Service Desk Customer role for the other one. 

Hi Solène - Welcome to the Atlassian Community! We need more clarity around what is not working.

Hi Serge - Welcome to the Atlassian Community! Try creating the issue as your are doing (but no link stuff). Then add a Branch for Most Recently Created Issue Then add a new action for Link Issue and choose the Duplicates link type. Use Trigger issue for the issue. Be sure to save and Publish. 

No, no hay un historial registrado para los cambios de formularios.

@Matthew Canham ??

Hi Leah, You will be better off asking Atlassian direction with a support ticket. https://support.atlassian.com/contact/#/

Os formulários são editáveis apenas pelos Administradores.

Hi Mike - Welcome to the Atlassian Community! You should be able to Filter on the JWM board by Epic. However, you can only see issues for a single Workflow at a time. So if your Epics are using a different workflow, that might be the reason. Click on the More link and chose the workflow used by your Epics if that is the…

Olá Tatiana - Bem-vindo à Comunidade Atlassian! Onde você está realmente usando essa funcionalidade? A sintaxe provavelmente está errada para onde você a está usando. 

Hi Tom - Welcome to the Atlassian Community! You would actually want to Clone the Epic and all of its children. The Marketplace app Deep Clone is probably the best thing to use. 

You can base the Swimlanes on JQL and do that, sure. 

Hi Leighton, You can create an automation rule based on Issue Transitioned trigger in the JSW project. Then add any Conditions needed to make sure it only happens for specific issues. Then add a new action for Create Issue. Choose the JSM project and all of the fields you want to populate. Then add a Branch for Most…

Hi Steven, I have never see than issue type from an out of the box Jira install. So I would say it is a custom created one.

Where in TN @tsmith ?

Hi Ismael, Unfortunately, I don't think you will be able to do that with out of the box JSM. There are some add-ons that might accomplish that for your such as: https://marketplace.atlassian.com/apps/1218221/feature-bundle-for-jira-service-management?hosting=cloud&tab=overview Or the Refined app. 

Entonces, ¿no quieres que se edite el formulario? ¿O no desea que se edite el problema creado por el formulario?

If it is not firing at all - even when the box is checked, then you need to open a support ticket with Atlassian for them to determine what is going on. Please post back here with the resolution so future readers will know what's going on. Good luck! https://support.atlassian.com/contact/#/

Hi Ben, Yes, you can have different workflows for different issue types. But you can only see issues associated with a single workflow at a time on a board. The List view though will show all of them. Finally, you could create a second board (Jira Software board - assuming you have a JSW license) and use it with your JWM…

Hi Rita, These are categories that Atlassian has identified and maintains. 

Hola @Admin JF No, no hay un historial registrado para los cambios de formularios.

Yep - one of the many differences between the two products. An alternative would be to implement an automation rule that will auto assign the user based on the project. Or course that's the same as having a default assignee. The best way would be to click the create button instead and create the issue that way. 

Hi Hugo, The closest you might be able to come to that is with the ScriptRunner Behaviours app. But not sure where they are with custom fields yet. Another workaround would be to setup a transition screen and make the user do a transition to Flagg an issue. Then on with that transition, you would add a validator for Field…