Nic Brough -Adaptavist- Expert

You wouldn't expect Epics to belong to many initiatives - look at splitting them up if you think you need this. (Dependencies are a different story of course)

We cant work without any information or context.

Use "Board Settings" to get to the configuration

No. I am saying that you should follow the upgrade guides given in the docs. They don't need any imports. Your licence is not locked to a version, all that matters is the end-date on it - you can upgrade to any version released before the end-date.

That screen is asking you what you want help with, it will ask more questions later in the process. From your talk of Atlassian.net and Jira - go with Jira Cloud

At present, a browser can only have one Atlassian Account session open, so the simple answer here is "you can't". You have to use another browser, or a private browsing session to log in a second account.

I am nor sure what you mean by "link is stretched", but the blocking is entirely down to ATP - you'll need to configure that so it allows them through.

It's how Jira has been designed and built since version 2.0 The resolution is not mandatory in the way other fields are made mandatory, it is defaulted and does not have an "empty" option when you put it on an "edit" screen (i.e. create, edit or transition). It always gets filled when presented to the user. The reason for…

Don't bother with the database, it's complex and you're looking at the wrong thing anyway. Go to Admin -> Global permissions and get the list of groups that have "can use" in there. The members of those groups are the ones that give you the 4953 (note, that deduplicates users - if you're in three of the groups for example,…

They don't use SQL for most of the user activity, it works off the local index, and the indices in the database aren't used much. You won't see any day-to-day performance improvements by rebuilding indices. Plus, a well-behaved database would not need to rebuild indices. Anyway, that said, there's no harm in rebuilding.…

Why are you upgrading bits of Confluence like this? A lot of the code is dependent on specific ranges of libraries, so you can and will break it by randomly changing parts of it. Best bet - undo your "upgrade".

Generally, we don't delete here - your answer may be useful for someone else! But let me know if you really want to delete - I can move it out to a "removed items" private area which we remove from after items have been in for a while.

Search for issues, the "issue navigator" will list them, and has some tools, one of which is "bulk edit" - use that and select the edit, you'll be able to set the assignee on the issues you've searched for (it has a secondary selection too, so your initial search does not have to be 100% accurate)

Natively no, a field is either visible, or it is not. (Generally, it's unhelpful to have people see different views, you're supposed to work together) It's a different case for Service Desk - issue fields do not have to appear for customers. There is a "field security" app by Quisapps which provides secure fields.

Log into the server and go to the directory I named above.

No. You don't need to worry abou them for Atlassian applications.

I would look to the cause of why you're having to do this. >Recently, when an issue is Completed within a Sprint, it automatically moves to the next Sprint even though it's been closed This is likely to be because the issue (and/or one or many of its subtasks) is not in the last column of the board when you end the sprint.…

We need to look at the application logs as I said before, not sure why you've looked at the audit.

I would want to read the application logs next Should atlassian-jira.log under <jira home>/logs/ (but check all of the files in there for errors being thrown as you refresh the dashboard in the browser)

It really is as simple as Admin -> Index -> Rebuild index Log in as an admin. Go into the Admin menus (cog at the top right near your profile picute) and look for "indexing". Use . or the search-admin field towards the top left of the screen to search for "index" if the menus are a bit overwhelming.

I'd use ScriptRunner, but I do work for Adaptavist, so that's always going to be my first answer. Powerscripts can do it, and I think Automation and Autoblocks can as well.

Um, your supervisor appears to have destroyed your index, so I'm not suprised searches are failing. For re-indexing, you should use Admin -> Index -> Rebuild index (use the full locking one). That applies for repairing the damage that's been done here too. It will rebuild it from scratch, re-creating the files it needs.

See https://confluence.atlassian.com/adminjiracloud/configuring-sub-tasks-818578898.html - bear in mind this is a global effect, the changes you make will appear on all issues in every project

Why are you importing? The standard upgrade methods upgrade your data as part of the upgrade process, you don't need to import anything from the old Jira.

Yes, that is correct. If you are unable to see an issue, then you won't see it. On the board, in the project, reports, dashboards and so-on. They all maintain the security.

You probably have the wrong owner or permissions on the directory it is unable to open. Make sure that the directory and its children are all owned by the user who will be running Jira.

Can you drop down to the command line, change to the bin directory and run the start-jira.bat file - the output will come to screen and may tell you what is wrong.

Looks like it.

If you have a date or date/time field, you're going to need to come up with a rule to convert it into a length of time

I suspect one of your inexperienced admins has added "unresolved" as a resolution. Go to Admin -> Issues -> Resolutions and rename it to "do not use this" to start with, then remove the resolution field from the "create" screen, then you'll need to assess the damaged issues with the broken resolution set.