Nic Brough -Adaptavist- Expert

I'd strongly recommend Botron's "Configuration manager" and Adaptavist's "Project Configurator". They take different approaches, but both allow you to move any and all project configs and data from one Jira to another. (Obviously, I work for Adaptavist, so of course I'll recommend our option. But I've worked with both of…

See the "importing attachments" section in https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html

Are you on Server or Cloud? Portfolio has two "views" on Server as well, there's a 2.x view and a 3.x view. Most of the docs look at version 3 now, but you can swap back to 2.x, which might be what you are seeing.

What do you mean by "Confluence Model"? Or, more importantly, what are you expecting your data to look like after moving it into Confluence?

You selected "server" when asking this question, but the screen you have given us is from a "cloud" installation (I know, Atlassian chose bad names for the three platform variants of their software) Cloud does not allow you to "upload" apps. You need to go via "find new apps" to get Cloud to talk to other systems that…

Short answer: It. Does. Not. Work.

Tequila... It makes me happy.... Seriously though, I'm expecting a heavy focus on Cloud, DC and Align on the technical side. 

What do you mean by "watch point"? And how would that lead to a "proper backup"?

First time I ran into "Issue created but not visible". Now, this is not what you've seen more recently in Community where people are on a board, belt "create" and get "issue created but not visible" because the board config excludes the new issue for some reason, but a much older case. I'm talking Jira 3.0.3. Where the…

Anecdotal. Over 25 years, I've yet to find anywhere that it works. I've found lots of places that desperately needed to stop doing it, several Jira sites who (including, as I said, ones run by people who, in other threads here, thought it was a good idea until it blew up in their face - one of them had the decency to…

The majority of the customers really really don't want it. This is an argument that has rattled on for years, even to the point where three people who were proponents of multiple assignees have ended up spending a lot of money with Partner or contractor support gradually unpicking the messes they've made of it. There's…

Everyone can see the resolution. You may not be able to set it due to workflow, but it is visible in the issue view, no matter who you are. It sounds to me like you have boards or views that are set to ignore resolved issues. I would get them changed so that they include them. Or just create your own ones that work for you.

Ok, random initial guess - check that the stories and tasks are using the same workflow. You have three unmapped status which makes me suspect the stories might be using a different workflow, with unmapped status (and if a status is not mapped, the issues in it won't be on the board or in the backlog)

You need your database administrators to not drop the database. That's something you'll need to take up with them

There is some difference in the issue that means the board is not going to display it. I would want to take one of their missing issues and compare it with * One of your issues which is not missing - apart from the issue key and the creator, what are the differences? * The board filter - this can explain why issues are…

Could you have a look at the 62 "ready for work" issues. What issue types are they? Stories (and issues at a story level), or are 50 of them sub-tasks?

The only way I can think of doing this is to create specific sub-tasks for time-logs and get your people to log story points on them. Making sure that the field they use is NOT used for estimation because that will not work. It's purely for counting. Also, use a board filter that excludes those issue types, or a…

"none" is what Jira displays when a select-type field is empty. It's not actually "none", it's <nothing here> I have not tried it for myself (as I'm not sure where you might be coding), but try def childOption = "" or def childOption = null

This happens so that the old key remains searchable when people have external issue links. In your example, the link to http://yourjira/browse/ABC-1 and ABCOLD-1 will both take them to the underlying issue. If you have database access, and a steady hand (I never recommend messing with a Jira database, but this one is a…

You must have an admin somewhere!

Do it if it is useful for your process. Some teams do not do it because they want the pool of work in a sprint to be genuinely fully handled by their self-organised teams. Some teams don't want their sprint starting until they know exactly who should be doing what (this is not quite the Scrum principle, as it only really…

No, they recommend using the databases backup tools for medium and large Jira systems. There are some more advanced tools that take uninterrupted database copies. A simple trick I used to use before the more clever tools came along was to replicate the database to a second database. When I needed a backup, I'd break…

By "wiped" @Lenin Raj is saying roughly the same as I did - a database process or person has removed all the data from the database. (I've said "dropped" rather than wiped because I tend to think of "wipe" meaning "remove all the tables and data, leaving an empty database", and "drop" to mean "remove the database in its…

No need to apologise for correcting this! It used to be the case that issue delete had nothing, but it does now.

I'm with @Lenin Raj here - if a workflow is inactive and hasn't been amended for thee months, then either its project is dead or a later version of it is working well enough or better than it was, and you can safely kill it.

I'd agree very strongly with that chain of versions. You might be able to skip 4.3 or a couple of others, but do NOT skip 3.5, 4.0, 5.0, 6.0 or 6.15 on the way to 7.2

I suspect you are using £ to represent Σ If I am right, then Σ is the mathematical short-hand for "sum of the following". Time Spent is a (calculated) field on an issue saying, well, how much time has been spent on the issue (usually calculated from the work logs). However, an issue can have sub-tasks, which can have their…

If you have Server, you can amend the .jsp and velocity files that generate them, but I'd strongly recommend not doing that, as it leaves you unsupported (and they're a fiddle, you have to work hard to do much with them)

For me Watching: I have an interest in this issue for some reason. Usually as something outside my direct working list of issues. I use it a lot on issues on the other end of links from my issues, and when I have any interest (for example, we give new starters a list of things to do. I watch the ones I need to report on,…

Just as a warning - you absolutely do not want the resolution on any screen other than transition screens (and view screens, but it appears there automatically so you don't have to think about them). If you place it on a create or edit screen in the screen schemes, it will get set incorrectly as people use those screens.