John Funk Community Champion

Can have the rule only apply to one project. Can you share the rule you have so far? And what's not working about it?

Hi Brian - Welcome to the Atlassian Community! You can restrict access to a project by changing the Permission Scheme for the project. Update the scheme to change who has access to the Browse Project permission. 

Hi Stuart, You should be able to do that with Automation For Jira. Here's some infromation to get you started. Once you have a rule started, feel free to post back here for additional help. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all…

That's a strange phrasing of the post function. But I am glad it is working!

Hi Michele, Yes, there is a free version of the server add-on Automation For Jira called Automation For Jira Lite. 

Hi Roja, Did you select the Clear Field post function? Because when I do that and select Story Points, I get this: "The value of field Story Points will be cleared."

Hey Kara, I think you have it right except for the Only users with Resolve Issues permission can execute this transition. Since it is a part of the Any, the anyone with that permission can execute regardless of the other conditions. So to solve that I would either move the Resolve Issues to a validator instead of a…

Hi Pablo, You can use Automation to transition the Sub-tasks when the Parent transitions. 

Hi Stephen, You have to walk it up the chain. Check to see what Screen Scheme the Screen is in. Then, check to see what Issue Type Screen Scheme that the Screen Scheme is in. Then go to the list of Issue Type Screen Schemes and see which projects are associated with that Issue Type Screen Scheme. 

Hi Silvia - Welcome to the Atlassian Community! You should be very careful about allowing the deletion of anything in Jira. It's usually best to include some type of status in your workflow such as Discard or Abort (Done type statuses). And just leave the issues there. But if you really need to delete them, you need to…

I cannot reproduce the problem in that scenario either. I would go ahead and open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

Hi @Service Desk Italarchivi - Welcome to the Atlassian Community! I am not able to reproduce the problem. Can you give us some more information? What type of project is it? Next-gen? Classic Software? Business? And what view are you using? Old Jira Issue View? New Jira Issue View? 

Hello and Welcome, @Remco de Ket !! We are glad you are here!!

Ah! Yes, then the screenshots above are correct. :-)

Hi Grace - you are mixing apples and oranges. You are showing screenshots of connecting a custom field to a context, which in this case is connecting an issue type to a custom field. But the post is about connecting Field Configurations to an issue type. Those are two different things. What exactly are you trying to…

Thanks for sharing @Gil ! How are you populating "status time"?

Hi @PraneethM , We accomplish that with a combination of the Permission Scheme and Issue Level Security. So that issues can only be see by certain people that are granted that permission. 

Hi Mia, There is an ongoing incident that Atlassian is working on. You can follow along here: https://jira-service-desk.status.atlassian.com/incidents/59sqc3gf0nhj

Hey Otto - You can follow along with updates here: https://jira-service-desk.status.atlassian.com/incidents/59sqc3gf0nhj

Apparently there is an ongoing incident with Automation For Jira right now. You can following along here: https://jira-service-desk.status.atlassian.com/incidents/59sqc3gf0nhj

Hi Preston, I would create groups for each of those roles. Then link the Group to the Role in the project settings. That way, when person leaves that role, you just remove them from the group, and everywhere that uses that role will be updated. 

Well, it says that settings have been changed 4 times today. Are you referring to the Cancelado one? If so, can you share the details of that one? (Mostrar mas)

Hi Victor - Can you share a little more information? Can you share the Audit log of one of the rules that was working but no long works now?

Do an edit on the field configuration scheme :-)

If you are on a board, then you can add the Issue Type as one of the 3 fields showing on the board to display the name. If you don't like the new detail issue view, then you can use the old issue view that shows the name of the issue type.

Hmm, I guess check the underlying board filter to see if you have access to the filter. Outside of that, I am out of ideas and would suggest you submit a support ticket to Atlassian. 

Add yourself as a board administrator and see if it comes up. 

Hi Katie, Unless I am missing something, why can't you create a new Field Configuration and then associate the new Sub-task issue type to the new Field Configuration in the Field Configuration Scheme?

Not sure that I would classify it as missing usability since you have the option to change a standard icon. But regardless, what exactly was the feedback that they didn't like about the different icons for each issue type? We have more than 100 issue types and lots of creativity with the icons so it is pretty clear what…

Hi Michele - Welcome to the Atlassian Community! Are you a board administrator? Or a project administrator for that Project?