John Funk Community Champion

Hi Silvia - You need to make sure that the underlying filter for the Board is shared with him. 

Hi Angelique - Welcome to the Atlassian Community! Have you done that last part where you need to modify the Permission Scheme for the project that you want to log time against? See that last sentence in your screenshot above. 

Hi Christian - Just to echo Jack's comments - I really would not delete issues. The only time we do it is for purely test purposes to try out something like a new workflow. And we only delete it to not interfere with metrics. Even then, only Jira System Administrators can delete something. We would CERTAINLY never do it as…

Olá Carlos - Bem-vindo à Comunidade Atlassian! Você deseja criar um relatório ad hoc usando JQL? SQL não está disponível nativamente para a versão em nuvem.

No, there is nothing about Issue Types in your rule that should prevent it from sending an email for the others. That would be handled with a Condition. Maybe there is something in the workflow for the other types that is preventing it for some reason? I can't imagine what that would be. I would go ahead and create a…

So it works like this - You have a Field Configuration Scheme. Then inside the Scheme you can have multiple Field Configurations - each attached to different issue types. In other words, you can make some fields mandatory for Tasks but not for Stories. Then you attach the Scheme to the project. So if you want Field Q to be…

Hi Kyle - Did you check the Audit log to see if it helps you any? From what you described, it should send an email every time an issue is created on that project, regardless of the issue type. 

Hi Raf - Welcome to the Atlassian Community! As Maili says, you can't at this time. The concept of Next-gen is that each is an independent project so copying one to create another one would automatically have shared components behind it, which is not allowed. You can follow the roadmap in Maili's link. But for now, you…

Yes - and then just change that one field out of the dozens or hundreds you may have. 

Hi Stephanie - Welcome to the Atlassian Community! You can also type gg for a keyboard shortcut while anywhere in Jira. Then type in Automation rules to get to the tool. 

Hi Silvia - Welcome to the Atlassian Community! The cards (issues) that show up on boards are based on the underlying filter attached to the board. So you can delete a board with no problem and it will have no effect on the cards themselves - they still exist and can be accessed. So, I would check the board filter for the…

You need a different field configuration for each project that has different required fields.

Okay - did you try to go into the Board Settings and make the changes there?

Hi Erika - What do you mean by Edit the field fields? Do you want to remove or add fields to a screen? Do you want to change the actual field itself somehow?

Hi Preston - You can do that by going to the Board Settings, then either the Card Layout where you can add a field. Or the Issue Detail View and add the Status there. 

Hi Joao, You can do that through creating a different Field Configuration for that project. See this guide for assistance on how to do that: https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

Hey Andrew - I certainly have not seen that behavior. Sounds like something you might want to submit a support ticket for with Atlassian: https://support.atlassian.com/contact/#/

Yes

@John McKiernan - Can you help @Ankush Dixit out?

Hi Calogero, Are you including the Reporter field when you create the sub-task? If so, what are you using as the value - you should select From Trigger Issue or something like. Can you send a screenshot that expands the Create 1 sub-task portion?

Okay - glad I could help a little. 

Hi Roland - Welcome to the Atlassian Community! We actually have a separate Workflow for Sub-tasks. Simply create a new workflow with the statuses you like, including where it goes when you create it. Then attach the new workflow to your project's workflow scheme and attach it to the Sub-task issue type. Then finally,…

Hi Patricia - Welcome to the Atlassian Community!! We use a third party add-on called External Data for Jira Fields. You can find it here: https://marketplace.atlassian.com/apps/1219994/external-data-for-jira-fields?hosting=cloud&tab=overview I hope that helps!

Hi Manfred - You need to modify the Field Configuration for that project. You can find directions/help here: https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

You have to put it in the Announcement Banner page: https://confluence.atlassian.com/adminjiraserver073/configuring-an-announcement-banner-861253135.html?_ga=2.170234468.513035551.1586779195-1313086432.1576012938 You can copy this CSS: <style type="text/css"> #project-field, #project-single-select{min-width: 500px;}…

Hi @anu - Here's a good example of one with several votes but has gathered some recent negative comments. How's the best way to see about getting a Product Manager to give an update? I have added a comment to help drive some civility, but not sure how much that will help. https://jira.atlassian.com/browse/JRACLOUD-17783

Hi Katherine - Welcome to the Atlassian Community! Yes, you can have users inside of Jira be able to see Service Desk issues. Just be sure that the users have access to the project based on the Permission Scheme attached to the Project. 

Great! Glad I was able to help. :-)

Hi Terry - Welcome to the Atlassian Community! Yes, you can do that with the Automation For Jira tool inside of Jira. For more on using Automation For Jira, see these help pages.

You have the option to apply a different Security Level to each issue or no security level at all. You don't have to populate that field.