Jack Brickey Expert

by default "Severity" isn't a field in Jira. Jira uses the singular Priority field. Now you can certainly add a Severity custom field and I have actually done this for one project. Just add a dropdown single select field.

oops...very sorry Rob. I did not notice this was OG. my brain didn't switch out of Jira mode. Yes I'm sure you can suppress notifications based upon TOD in OG. Here is an article and video that might assist - notification-rules 

there isn't a button to start/stop a clock. you basically just use log time. the methods differ from Classic and NG and even on what screen you are on. Below is an example of one method. while in detail issue view click on the time tracking area. if you don't see time tracking you need to add it to your screen

Hi Rob, not w/in standard Jira notifications. Two things to consider here: * maybe you could disable notification and use Automation to replace notifications. Unsure how successful that would be TBH...just a thought. * consider an addon app, for example smart-notifications . I have no experience w/ this specific addon and…

Hi @Velizar_V , well it appears that Atlassian rolled out a change that may have killed the hack-around I suggested here. Here is a thread where I covered this before - Next-gen-workflow-How-to-add-a-second-done-status Here is an image of my test NG project where I performed this, note the new done is Done2 (not just a…

So as it says you can only have a single Done status. Are you trying to have two statuses in the done category or are you trying to change so that Rejected becomes the one done status?

To achieve this you will need to creat a separate Classic Kanban board and choos your profile for the Location field. Then you can use Add item in the sidebar to add a link to the board url. Be sure to share the board. You can then have access to full Kanban board settings. 

Understand, I don’t use initiatives so things certainly may be different here but I can’t help but hope it is achievable. I have access to a premium test system so may try to play with it later today. 

Unless something has changed (haven’t tried lately) you cannot. Here is the work around. * create new request types that mirror the old ones with slightly different names , e.g. add “new” suffix and associate to the new issuetype. Keep these hidden from portal for now * using bulk edit change all existing issue from the…

@eric.liangoridis I suggest you creat a new post for your questions. 

Can you provide your exact JQL? I would think you could use the following. ...AND issuekey not in (a,b,c) or “epic link” not in (a,b,c) The first part covers the actual epic issue keys and the second covers the issues that are part of those Epics. 

So this appears to be an addon app you are using? I’m unfamiliar with that icon in your video. I recommend reaching out to the vendor of the app directly. You might also check a different browser but I don’t suspect that is the issue TBH. 

There isn’t any trigger that occurs from a user clicking on a field. Maybe there is a different way to achieve your actual end goal rather than the suggested implementation here. 

Could you share a screenshot. I’m not sure what you mean by column when referencing the Backlog. 

almost makes we want to move to Premium. ;-)

Those instructions, and the app are for Server only. For cloud you don't download anything since your instance is in the cloud. First you need to have permissions to add apps. Click on Apps in the menu bar then Find new apps. Now unfortunately what you will not find there is any dark mode apps for Cloud.

in classic projects you turn this on under Board settings. Roadmaps are associated with boards. Here is some documentation - what-is-the-roadmap 

Hi Sandra, welcome to the Community. Can you provide a bit more info here? When you say you added a value to the dropdown list can you explain how you did this? This is generally done by going to the admin section (COG) > Issues > Custom fields, find your field and click on the ellipses and select contexts then edit the…

good question @blim . Here is my top-of-mind list: * Conditions - approval, hide from user, only assignee, permission, user in xxx, value in field * Validators - i use Checklist Pro and use the "all checklist items are completed", field required, field modified, parent status, permission, user permission * Post functions -…

that is indeed an odd error. I saw another post this morning where the user was getting the first error when trying to create an issue from an epic. I would recommend you reach out to Atlassian Support and have them take a look especially if repeatable.

Hi Ross, have you perused the docs? There are some good guides to get you thru this I think but maybe you are looking for something else? https://support.atlassian.com/jira-service-management-cloud/resources/ 

no manner of doing that today as folders. Maybe a link to a confluence page and w/in the page have shortcut links.

or what about the created vs. resolved gadget. i find that one of the more useful.

you must share the JQL filter as well as the dashboard. View the filter and edit the permissions.

I see. I don't have Premium which has AR so don't have experience w/ the notion of Teams. I found a couple of articles in the Atlassian docs but wasn't very helpful around this topic. You might scour the Atlassian docs a bit and see if it helps. Good Luck!!

The way JSM works is that you build the form inside the request. that form will be exposed in the portal so your customers would go to the JSM portal and click on the request type and fill in all the data in that form then click send. that’s how the tickets are opened.

The only dark mode option is with the Jira Mac desktop app. 

@Michael Kimathi _AC Nairobi_ Kenya_ , you never cease to inspire me. I love they way you look at life. The Community is so much more complete with you being a part of it!

yep it is really the attachments that consume storage.

here is what you do. Move all "Done" issues to "Resolved" then delete the Done status in the workflow editor and make Resolved = done category.