Jack Brickey Expert

Project > Project Settings > Notifications inspect the notifications where you don't want the user to be notified. For example Comments or Comments Edited, etc. There will be roles listed that conveys who gets notified. You need to the go to the users that you don't want notified and ensure that they don't have these…

Hi Janes, the board filter is the primary filter and the quick filter is a 'sub-filter'. In other words, if the primary filter excludes issues you cannot use the sub-filter to override that and display issues filtered out by the primary.

there is (or should be) a dropdown at the top of the report to select from.

Hi @Bernadette Buck , indeed this field type is not yet available in Next-gen. I expect they will add in the future.

It absolutely should not take two days. Please contact Atlassian Support.

I took care of this. There seems to be quite a few false quarantines lately and I have reported in hopes to have the filters refined.

Portfolio can be used on Server. “Roadmap” that you reference here is Cloud only and I expect it will remain as such as it is tied directly to Next-gen projects.

Warren thanks for sharing. Yep time management isn’t what I would hope for either. To be honest the old view presented challenges for me too but got used to it and, as you stated, was flexible to allow all necessary adjustments. That is a very timely comment on the date fields. I was involved in a question in the Community…

Great input Jimmy thanks for sharing. Agree that being able to turn off or switch back and forth is the right approach. Interesting note on the cascading fields. TBH I hadn’t even run into that but do have a few projects where that is used and will need to have a look. For sure that will be a big issue for those folks…

Change the boards filter and add “order by createddate asc”

Go to Jira settings > issues > custom fields and find your approvers field and click Configure. In that screen click the Default values and add your approvers

if the contributor (collaborator) is currently a JSW or Core licensed user then it will have not added cost implications.

It is hard for me to assess w/o actually seeing what you are experiencing, hence my request for screenshot. My current advise would be to delete all boards and start over w/ new board and set up the backlog to be for your To Do status. I'm assuming you are on cloud and that you are using a classic project and not speaking…

Before I share things I would like to see changed, let me say that I'm really loving the app from a user perspective. That said 75% of my efforts in Jira are from an admin perspective which the client app doesn't offer so while my Mac users may use this exclusively I will unlikely switch back and forth but time will tell.…

I’m trying to understand the scenario where you have a backlog without a board. Can you share a full screenshot of what you are experiencing. There are different types of boards and projects that can change the answer.

It isn’t possible to hide partial issue info. You can use issue security to setup permissions at the issue level. Have a look at this article - configuring-issue-level-security 

The issues will continue to exist in the associated project(s). What shows in the backlog depends on the backlog. If it represents issues in “To Do” status then those issues should be there but not issues in say In Progress, etc.

Have you deactivated the user account? Have you queried for all issues assigned to, watcher, reporter = EB to better understand the history?

Have you clicked the “change Template “ link under the IT Service desk image?

Well you could simply use project = myproject which will return all issues. You can tweak from there. 

The behavior I generally get if I enter text and enter the i am placed into a JQL search. For example... if I enter “hello-“ <enter> then I get the image below. Now if I am entering an issue number if I do so to quickly and hit enter I will get the wrong issue at times. I have to let the search complete and the select.

well nothing OOTB really. Consider addons or even Portfolio for Jira. Other consideration would be use Confluence in conjunction w/ Jira and Epics. Depending on what you need in a calendar view you might be able to create something useful (sorting by due date, target date, etc.)

unfortunately not. Delete is forever. The only recovery is if you are doing backups and you restore from backup but chances are you will lose changes w/ restore if any time has lapsed. The best course of action is to not give anyone "delete" permissions.

ah yes. that is indeed the case. You might want to provide feedback directly to Atlassian either thru Atlassian Support or via the Give us feedback link under your profile icon

there are two such gadgets for cloud. unsure which you might be looking at but, to answer the question in the title of your post - both are for cloud. time-in-status time-in-status-for-jira-cloud as far as the accuracy I cannot speak to that as I do not use either but might be able to comment if I had more info as to what…

Hi Chris, So the best answer depends on some details. But let's see if we can flesh things out here... First you could consider configuring your board (assuming it is Classic and not NG) so that swimlanes are by Epic. This would illustrate all Epics that current have active issues on the board. What it would not show is…

Beef (aka 48879), not sure what you are referring to and if there is a question here or just a statement. Could you clarify? Maybe a screenshot?

yep i think that is my recollection as well. I did find this thread that might help. TBH, i need to research more on this myself. I expect there is much discussion here in the Community on this and possibly suggestions in JAC.

you won't always have a button to add a status from the board itself. that is available with simplified workflows. Edit your workflow and add the statuses you need and build the transitions as desired. Return to the board and you should have the statuses available to map.

resolution = unresolved ==> all issues currently in the unresolved status resolution was unresolved on now() ==> is a malformed JQL please use resolution was empty on now()