Nic Brough -Adaptavist- Expert

Next-gen is not a separate product, it's a new way to handle Jira projects - different UI, different approach to the "classic" style projects. It's supposed to be neater, faster and more easily administrated and customisable by the usrs than classic projects, but they do not yet handle everything classic projects do, so…

Burn-down is calculated when you deliver what you said you would, not when it's part way through. The only way to get this to show burn-down for in-review is to have that step considered as "done", which you can do by moving the status into the last column on the board (which means "done")

That is essentially "how to write your own 3rd party application". If you're willing to do that just to avoid using someone else's app, then yes, it's a good place to start. It would be worth weighing up the reasons for not wanting a 3rd party app - if it's purely cost for example, then you are probably going to find it…

Probably the users are different and can see different issues. You'll need to look at the data on "missing" issues to see why it is missing from one search and not the other.

What does the log say the problem is as it starts up or tries to serve?

For an issue to be "done", it must be in a status that is in the last column of the board (as do its sub-tasks). If an issue is not in the last column when you end the sprint, it will move into the next sprint, as it is not done.

Ok, so the next two steps are: * Get someone else to try attaching the same file to the same issue. Does that fail as well? * Read the application log file to see what the underlying error is

Backup and restore will totally destroy the target Jira, it will be completely overwritten with the backup, you'll lose all the projects and issues in it. You need to do a merge instead - see https://confluence.atlassian.com/jirakb/merge-multiple-instances-of-jira-cloud-779160767.html

Only if the Discord accounts are created in a directory you can use with Atlassian Access.

There is no way to do this directly, but there is a cheat. If you apply an expired trial licence to Confluence, it effectively becomes read-only - admins can still do admin, people can read pages, but no-one can create or edit pages.

Not natively, they're in the menu because Atlassian's designers think they are not that useful to be presented immediately. If you have ScriptRunner, or are willing to write a short app, you can make use of "web fragments" to add elements to the main display - these can be buttons that are effectively replicas of the menu…

Could you describe what "unable to attach" means? Error message? No option to attach? Drag and drop does nothing? Large penguin sitting on the keyboard?

If you are getting the pop-up screen with resolution on it, then that should set the resolution to the selected value. However, if it's not being set, then that suggests that you have a post-function on the transition that says "clear the resolution". You'll need to remove that.

Your findings are correct The "Atlassian Agile coaching" article is a little misleading as it doesn't explain that their upper level alongside Epic is simply another type of story-level issue with some links and reporting that replicate some of the Epic functionality. That's broadly what Structure does too - its layers of…

When it is ready. Atlassian do not give fixed release dates, as they don't want to be forced to release stuff before testing and bug fixing has been signed off as working.

You will need to set up an LDAP group with the people you need to be admins added into it. You can then go to global permissions and add that group to the list of groups that have admin access to Jira.

No, the assignee field is deliberately a single user, to prevent the problem that inevitably happens in that multiple assignees think someone else was dealing with it. In real life, you absolutely need to be able to point at a single responsible human. If you want to nominate secondary people who may have some joint…

Yes, they will move you up to a tier that supports your usage. I'm afraid the tools for monitoring storage really do come down to "look at your account" The space used by individual spaces is not useful though. Everything is looking at total storage, not the details.

It will continue to work, but on Cloud, you will need to expect an "upgrade" on the billing side - when you run out of a standard amount, Atlassian will just move up to the next one and charge accordingly.

>Do you need to define 3 groups for that model? Strictly, no. Only two. You could skip the "confluence-users" completely, and just allow "internal-users" and "outside-users" groups to be the only login groups. But, yes, if you get the view access right with your two differentiating groups right, there should be no…

You have to grant access to the space for people to be able to see the pages within it. I'm afraid your "I know that I could probably add confluence-users and outside-users to the space and then restrict each page to list confluence-users and then add outside-users to the restrictions to that one page" is not far off what…

Quick filters are for narrowing down the current selection further, not drawing more issue into a board.

Sorry to have to ask, but I just want to be clear that I have understood your process correctly. I want to repeat it back to you in my words, and hope you can tell me that I have got the right idea. So, * You click "create" and get a box asking for project, issue-type, summary, some other fields, and a reporter and an…

From where are they getting the notifications? I mean, what are they telling this other person? Things like "person X edited page Y"? Or something else? If you're not sure how to describe it, could you get a copy of one of the emails and give us an idea of the shape of it? Ideally, get the whole email, but anonymise any…

The workflow is the steps an issue goes through as part of your process, with each step having a name (status). A transition is an action, trigged somehow, that moves an issue from one step to another. So, "when the issue is closed", that is being done by someone clicking on the trigger in the ui (or an automation or…

Edit the workflow, finding and editing the closed transition(s). Add a screen to them, one that has the resolution field on it (doesn't need any other fields)

You can use your own identity provider with Atlassian Access.

Question: You say "The current process they are using is cloning the task, deleting any subtasks not assigned to them, estimating their subtasks, copying that information back over to the original task, and then deleting the cloned subtask". Why are you doing that? Why not just put the information on the original task?

You can't do this on Cloud, it is done by code, there's no configuration for it. Best you can do is to set a default, so that people will tend not to leave the field blank, but this does mean you'll end up with a lot of junk data lying around.

No, it's needed there so you can change the project type.