John Funk Community Champion

@Andy - PTC Redundant - Well done! And definitely inspiring. :-)

Hi Harris, Have you checked the Issue Type Screen Scheme on that project to see what screens are mapped to to what Issue Types?

Maybe the History will be the most help. 

Hi Patrick - Welcome to the Atlassian Community! What add-ons are your using? ScriptRunner? Automation for Jira? Something else? It's problem in one of them. If you look at the history of the new issue - who does it say created it?

Okay - post back here how it goes so we can get this closed out. :-)

Hi Helen - have you check the Notification Scheme attached to the projects that the user is not receiving notifications for? Maybe the scheme does not send them?

Sounds like you are on the right path. Please post back a reply here to what you found out so we can close this one out. :-)

I am not familiar with that one. The other option would be to come back right behind it and null them out using something like Automation for Jira or ScriptRunner. 

Hi Vika - Welcome to the Atlassian Community! The ability to view or edit a custom field on a screen depends a lot on whether the field is actually on that particular screen. First, check the screen scheme being used for that project to see if the field shows up on any of the associated screens (Create, Edit, View). 

That's very strange - I have a test Next-gen project and it does not populate those fields. Do you use any other add-ons like ScriptRunner or Automation for Jira that might be populating those fields?

Is it a Scrum project?

Hi Irena - Welcome to the Atlassian Community! What type of project are you using? You should be able to check the workflow for that project and see what is happening when you execute the Create transition of the workflow. 

Well, maybe not a "system" field by name - but it is treated that way. It should have the designation of "LOCKED" beside it. In other words, the Jira system is looking at that particular field when it makes certain changes in the system. 

There should be a group in your list of groups called site-admins. It is members of that group who have the ability to manage users. 

Sorry - yes, you should contact Atlassian support. 

I am not aware of a way for the user to see that. 

It’s never good to change the name of or otherwise mess with the structure of system fields. You are better off creating a new custom field for your purposes and migrating the data to that field.

Sounds good - sorry I wasn't able to provide better guidance. 

So if they created the issues, then you should be able to run the Permission Helper and choose Edit Issue for the ones they can't edit. 

I am at a loss then - you should open a support ticket with Atlassian. :-(

So, you created a new Scheme from scratch that did not include those Issue Types. And then system on it's own added those issue types into the new Scheme? Is the project a Scrum project? 

Hi Daniel, You might want to try the Permission helper to see what it says. Got to the Permission Scheme in question and click on Permission helper button at the top right. Then enter one of the users that can't perform the function, select one of the issues they are having trouble with, and then finally the Schedule…

Hi Andrew - Welcome to the Atlassian Community! You probably just want to create a new Issue Type Scheme with the issue types you want to use. Then attach the new Issue Type Scheme to the Project(s). I hope that helps!

Hi @[deleted] - Welcome to the Atlassian Community! You can handle what users can do on a project with the Permissions Scheme attached to the project. You can grant the user to Create Issues on the project, but not Edit Issues on the project. 

For Opened vs Closed bugs, there is actually an existing gadget for the dashboard called: Created vs. Resolved Chart But that one will have to be a different gadget for each project and does not group by project. 

For tickets closed in last month: issuetype = Bug and status changed TO Done DURING (startOfMonth(-1), endOfMonth(-1))

Hi @Giuseppe Terrasi - So, sorry, I have been out of the office for the last month. You can create a filter like: issuetype = Bug and created >= startOfMonth(-1) and created <= endOfMonth(-1) That will always show you the Bugs created the previous month. See if that is what you are looking for. :-)

Hi Victor - Welcome to the Atlassian Community! Boards are based on Filters - so review the filters for each board to see what cards are supposed to show up. Also, just to make sure, check the permission scheme for each project to be sure the user has the Browse Project permission. 

It is just a group in the list of all groups under settings > user administration. It is for both server and cloud 

Hi @natia - Welcome to the Atlassian Community! Try removing the user from the site-admins Group in Jira.