Nic Brough -Adaptavist- Expert

You don't. This is one of the reasons that you shouldn't be looking in the database - it does not hold the data you are thinking of in a way that is easily findable. The workflow simplification data is calculated by the board, not stored in the database. You need to use the UI or REST API for a board to see whether a board…

Welcome to the Atlassian Community! You have no access to the Jira database on Cloud, and never will have. You don't want it anyway, it's the worst possible thing to look at if you want to report on Jira. You will need to use the REST API which is far nicer to use than the database, or, if you have a premium subscription,…

Yep. Make sure that you never add the resolution field to a create or edit screen, it should only be used on transition.

I'm afraid it's the same answer - either your authentication is wrong or your create issue screen doesn't have the right fields on it.

Confluence doesn't store or log searches, so there's no way to do this.

Welcome to the Atlassian Community! I am sorry that I do not quite understand the question, and need to ask for a bit more detail. What "login details" are you looking for? When someone logs into Jira, Jira uses the configured identity provider system(s) to ask the user to uniquely identify themselves, so that it knows…

Welcome to the Atlassian Community! This isn't something that's easily implemented in Jira Software. I think it is because it is missing one of the points of doing Scrum. When you are doing Scrum, you should be constantly looking at what is going wrong and why you are failing to deliver what you said you would. If nothing…

Correct, the category is more like a field than an Epic grouping. So while there's no "show me this category", you can of course search for it - JQL (and the basic search, and a lot of the reports) let you say "list the issues in this category".

Yes, many times, it's certainly not uncommon to find people migrating from Asana to Jira (all its flavours, not just JWM). Most of the ones I've done have been along the lines of * Housekeep what we've got in Asana, cleaning and changing the shape of items to be more aligned with the Jira issue setup we want to be using *…

Epic Link doesn't lend itself to default values, because that's not really how Epics are intended to be used. The person creating a story should be informed enough to know which Epic an issue should be attached to, or if they do not, be able to leave it empty for someone else to link it if needed.

I don't think there's any negatives of having one sprint end on one day and the next sprint start the same day. Most Scrum teams I've worked in or with do it, but with some variations. Most have a routine which is broadly * close the sprint * do the retro * (sometimes) have lunch * have a chat about whether the backlog is…

Welcome to the Atlassian Community! Jira email handlers will look at the subject line of an email, and if they find an issue key, assume the email is intended as an update to that issue. Check the headers of the emails people are sending when this happens, I suspect you'll find an issue key in them.

Welcome to the Atlassian Community! Jira does not have GraphQL functionality in it.

Welcome to the Atlassian Community! You'll need to take this up with Tricentis - it's up to them where they can provide their services.

Welcome to the Atlassian Community! Swimlanes do not define "done", it's the columns that do it. Are your completed issues all in the "done" column (the last, rightmost, column on your board)? Insights, like the board, only looks at issues in that column. Once it sees an issue in that column, it looks to the estimate on it…

There's a bit of technical detail I want to add to this. (Which is going to sound pedantic, because computers are very pedantic) Simple field validators check that a field is filled or has a certain value given some conditions. The comment validator you have chosen is not checking that there are comments on the issue, like…

It's not an assumption, it's from understanding what the backlog is, and what it is for, alongside what a sub-task is and how they work. A backlog is a list of issues (stories usually) that are items that could be drawn into a sprint. The purpose of a backlog is to rank those items into the order that the team should be…

No, I'm not stalking you. I read the question, I know the questioner has resolution on the create screen, I was simply explaining how it works and what they need to do to make it work properly. I am sorry you don't like being corrected, and for my (probably harsh) tone in my correction, but please don't let my response be…

Ok, great, we can clarify that. Epics and Categories have a similar reason to exist - they are for grouping issues together for some reason. Where they differ is that Epics are primarily an Agile artefact, used for grouping together a large pile of stories from across your entire issue tracking system(s), all the stories…

I'm afraid your use cases do not change the way things work. You can't associate screens on arbitrary actions that do not normally need them. If you were to move these actions into your workflows, so that they become part of the path to being done, you can add screens (and more) to them, but that's the only way to add…

Oh, and on the PS - that will only work when the configuration for the two issue types is identical. Which is fine for a short list of issue types, but begs the question of why you have many different issue types that all work the same way in larger lists.

It's not a design flaw, it's the right way to do it. This isn't coming from "a long experience with the implementation", it's coming from "a long experience in support and development, using issue trackers to capture and help deliver things people need". If your users are not able to select the right issue type up-front,…

Welcome to the Atlassian Community! Ok, you'll need to reach out to the vendor, it's unlikely anyone watching this thread will know much about it, so pinging them is much more likely to get a useful response!

True, that's a fourth category to ask about!

Archiving issues (or projects) will not affect your storage space. Archiving removes nothing; the data remains on the disk. It's just found differently. You're using 125Gb now; if you archive 100Gb worth of issues, you'll use 125Gb afterwards. To bring disk usage down, you need to delete stuff completely. Now, most of the…

Welcome to the Atlassian Community! Please, don't SHOUT AT US. It is hard to read, and some people find it rude. Jira Cloud has Automation enabled automatically. You can just go to a project or the global Admin -> System, and you'll find the links to automations for setting them up.

So, you did have an automation in place. Interesting that a deleted power-up was still active, I have not seen that before.

Ah, you can't if you're using the same transition. @Paul O has spotted that problem!

Nope, we're not your admins, you'll need to ask them, or Atlassian if you don't know who your admins are.

Welcome to the Atlassian Community! You can use as many projects as you like, all created with different templates. Your users can be added to as many as they need to be (the licence count is by "can log in", not by project)