John Funk Community Champion

Hi Nishad, We use the add-on JMWE to create issues during a transition. It works great for that. 

Hi Leah - Welcome to the Atlassian Community! When you go to create a new board, what are your options? I use Cloud so not sure if Server gives you the same options or not. Maybe try creating the board from a saved filter if you have that option. 

Agree with Tom below - see if a re-index will solve it. 

For the Next Gen project, go to Project Settings while on the Project and then click Issue types. You should see something like this: Then click on Add issue type and see if the new one pops up in the screen. 

Hey Heather - Welcome to the Atlassian Community! That's very interesting. Can you provide a screen shot of each views?

Hey Karen, After creating the new Issue Type, it needs to be added to the Issue Type Scheme that is being used by the project. Then it should show up as an option to create under the Issue. 

We had the same internal request hit us this week. We have not been able to figure out any good solution for it other than if the pain the user feels when they forget to hit the check mark to save it. 

The ones that do not have a value in the Fix Version(s) field should not disappear. Can you do a screen shot of an issue that disappears? Or can you post your base query here?

Hi Ankit, Do your issues have a value in the Fix Version(s) field? If so, that is what is causing the issues to disappear from your board when including the above sub-filter. For sure after you do a release the issues will not be displayed on the board with that sub-filter in place. What is it that you are hoping to see on…

Hi Thomas, If an issue is already in a status other than Backlog, you should need to have a transition in your workflow that allows issues to move from that status back to the Backlog. Then you would see it show up on the issue to be able to set it back to the Backlog. 

Hi 1on1 - Welcome to the Atlassian Community! There was a bug introduced to Jira for notifications a couple of days ago. You might try another test to see if what you setup is working now that the bug is fixed. 

Sorry that didn't work out, Jakub. Maybe you could add a question to the Transition Screen to ask them if they saved their changes first? Or remind them to save them. Otherwise, I think the add-on will do what you need. 

Hmmm, wondering how your system is labeling what makes a user inactive. Can you find that out from your system administrator?

Hi Rachel - Welcome to the Atlassian Community! Just did this same thing yesterday. :-) Try this: assignee not in (membersOf(jira-users)) Hope that helps!

Ah, I misunderstood then - thought you were only wanting to control access to the boards. We use Issue Level Security to hide individual issues from users. That can be based on groups, individuals, project roles, etc. Let me know if you need help with implementing that. 

Hi Brian, You can control access to each board by controlling access to the underlying filter for the board. If they use the same filter already, I would create a second filter for the second board even though it might have the same code. Then I would grant different permissions on each of the filters for who needs access.…

Great! Glad it finally worked for you. :-) Can you click on the Accept Answer button above so this one gets closed out? Thanks!

Marco - can you post a screenshot of the workflow for one of the types that is not showing up? Also, is the status Backlog in your workflow? Is the Backlog status mapped to your board? That message will show up if you have it go to Backlog on create but that status might not be shown. 

Great! Can you click on the Accept Answer button so the discussion will get closed out? Thanks!

Hi Rohit, For those types of needs, I usually create a simply filter first. In this case maybe something like: project = ABC AND created <= endOfMonth() AND created > endOfMonth(-3M) ORDER BY created ASC (there are several ways to calculate "last 3 months). Then I create a dashboard or use an existing dashboard and place a…

Very perplexing! Do the different issue types use different workflows? 

Hi Bhupendra - Welcome to the Atlassian Community! We use the JMWE add-on to do lots of things, including creating multiple other issues when certain issues are created or when an issue is transitioned to a particular status. 

Hi Giovanni - Welcome to the Atlassian Community! If it is a field that does not exist already, you can add a Custom Field in the Jira Settings if you are an administrator. If the field already exists and you just need to add it to the current screen, then you modify the screen to add the field. Are you using Cloud or…

Hi Vivek - Welcome to the Atlassian Community! The way I usually about that is to first create filter that shows all of the stories closed in the last month: issuetype = Story and and resolved >= startOfMonth(-1) and resolved <= endOfMonth(-1) Then I create a dashboard (or add a gadget to an existing dashboard) with an…

Hey David, If you are using the old JIRA issue view, you can click on the Transitions tab under the Activity section. Those values are also available through the API. And there are some free Chrome extensions that might provide some insight. BUT, you can't just do a JQL query to show those dates/times. Now, having said…

Hi Arik, You might try changing the Staging status to a Done statusCategory. It might let you do a Release from that column - you would just need to try it out. But in that process, don't set a resolution. 

Hi Marc - Welcome to the Atlassian Community! I don't believe you are going to be able to do that as described. You might try a different filter (or quick filter) that only shows those values. Or you could add another field that is only populated for those values and then do an order by on that field and second order by on…

Hi Manikandan - Welcome to the Atlassian Community! I am not sure that I completely understand what you are wanting to do - can you help clarify a little more - maybe even with a screenshot? You could show the Status field in the card if that helps you - go under Board Settings then Card Layout. I hope that helps!

Hi Ben, You will need to create a Support Ticket with Atlassian to get the suggestion in their queue. I also assume you simply moved the Backlog status from the Backlog section under Board Settings. As a side note, just curious why your team did not like the Backlog option. 

That's why it is based on Watchers - which you can opt into or not on each issue. That way you decide for each issue if you want to receive notifications. Having said that, Notification Schemes are shared across the organization - they may apply to only one project or many. But they certainly are not personal schemes for…