Nic Brough -Adaptavist- Expert

I think it's important to point out that Agile in general works with Scrum and Kanban on the concept that Board = Team. Also, teams are supposed to be mulit-functional, you would not have a developer and QA teams separated - the team delivering a story would develop and QA it all themselves. Once you understand that is…

Automation can send emails, yes.

Automation is not the way to do this (because it would make it look like the Automation has destroyed data that the user deliberately entered), you need a condition or validator on the workflow.

Automation can set a user as the assignee depending on selections in other fields, yes. Trigger it on change, use set field (assignee) as the action, and get the user to assign with a simple "if" on the smart value.

That's a perfectly good hierarchy, it shouldn't cause you any problems, as long as you explain it well to your Jira users (which is, for most people, going to take you less than a minute!) My point was more about the suggestion you made about having multiple hierarchies. You can only define one global one in Jira's…

Welcome to the Atlassian Community! No, this property is there to support the unusual way that the resolution field works - it's global and can't be configured by field contexts like custom fields can.

I'm sorry, but that article is a red-herring too - it's not screens either.

The field you have highlighted is not a status. The status is "under review". It is the resolution of the issue, set when "this issue needs no further attention". You should only ever resolve an issue when it is going into a "closed" status. Your screenshot is of what I call a "quantum issue" - it is both open and closed…

I'm afraid this is a "red herring" - this has nothing to do with field configurations.

Adaptavist use it for our managed services, product support, and Assist (Atlassian admin as a service), as well as internal support.

You should think of a Jira sub-task as being a fragment of its parent story. A simple analogy might be "Story = jigsaw, sub-task = single piece"

How are you doing your classification? What are you putting on issues to classify them?

Generally: * Pro: better project organisation and visibility at higher levels * Con: Complexity for the people dealing with the stories But for both of those, you could argue that the people affected shouldn't really need to have to worry about them - people generally don't need to look more than one step away from the…

What exactly do you mean by "cached"? The password hashes (Jira never stores a password, because you shouldn't do it in anything other than a password safe) or credentials are used to authorise a "session", so in that sense, they are cached, you couldn't use a system that doesn't do something like that (imagine having to…

No, I don't recognise it. But at a guess, it's probably one of the thread apps Might be best to ask your admins what they have installed that might be doing it.

Are your issue status ALL mapped into columns on the board?

The backlog is using the same filter as the board to which it belongs, it's selecting issues based on some criteria (often as simple as "project = X") It won't show archived issues, but I'd guess that the stories you are seeing are not archived. Archiving an Epic has no effect on its stories. You'll need to change the…

This feels like quite an odd question. I'll try to keep this one short, I have other questions, but there is one critical core question: Why are you using Confluence if you don't want to keep your content in it? (Immediate follow up - why do you want to put a copy into Drive/DAM/local storage/etc?) And then, which of your…

Depends on the type of indexing, but generally, it's simple - * Have you changed field settings? * Have you got people reporting searches not working? * Have you just upgraded with the auto-index flag turned off?

Welcome to the Atlassian Community! The key is necessary for communicating with other SSL protected systems. If you were to remove it, Jira would no longer be able to establish connections (application links) with them.

None of your updates to that issue have closed it. So there's nothing to burn down on.

This suggests that "eero" is blocking parts of your VPN. You'll need to talk to them - Jira does not do anything clever here, it accepts a connection on a standard port and talks to it (as long as the connection is whitelisted if you've enabled whitelisting)

>This is where I think Atlassian underestimates how big companies that use their software work. It's the opposite - they've moved into competing directly with other issue trackers that think they know how big companies work, and their successes in that area is a testament to them actually doing it right. Legacy systems…

Welcome to the Atlassian Community! You will need to restore your system's database to the backup you took before modifying the database directly. You should never alter a Jira database other than when Atlassian support tell you to.

Depends on what type of user object you have got, but I tend to work with "applicationUser"s. This is because when you do stuff like issue.getAssigneeUser() you get an ApplicationUser object. If you are working with them, then it's really easy to get a name from that issue.getAssigneeUser().getDisplayName() will fetch what…

Is it possible that you do not have view access ("browse project") to see the issues in the project? We know you are an admin, but that does not mean "can do everything". And, are there other projects using the current workflow?

First thing to check is if the board config includes the status the issue is currently in is mapped into a board column. There's another question here though. "Done" means "needs no more work", so it shouldn't be appearing on a future or currently active sprint (unless it was marked done during the current sprint)

On server, it is a lot more compatible than Cloud - Scriptrunner can get deep into the Java API, and can reach into the Advanced Roadmaps code. But Cloud has to do it over much more limited APIs, ones which we'd like to be extended in Server as well,

Welcome to the Atlassian Community! What types of field are doing this? I suspect you'll find they are text, not numbers, so sheets is importing them as text - it needs the ' to tell it the cell is a string.

Given the two filters you have, you should be seeing "Support" issues on both boards and in the backlog. So assuming you have no quick-filters or a Kanban sub-filter enabled, then I would have to say your board's column mappings are wrong. Are your issue status ALL mapped into columns on the board?