Nic Brough -Adaptavist- Expert

Ok, I was thinking of the server import when I said "key". When you are mapping your columns, it does not matter what they are called in your CSV, but for updating issues, map the column with the existing issue keys (ABC-123) to be updated on to the "issue key" that is offered in mapping.

Edit and issue that you expect to see the field on, it'll show the field name in the edit screen.

Sounds like a good description of "sub tasks" to me. For Server, DC and Company-managed projects, your jira or system admins will need to add one or more sub-task types to your project (via the issue type scheme). Once that is done, you'll find anyone who can create issues in the project will have "create sub-task" in the…

Ah, yes, I'm sorry, I was not clear in that the change to the transition will only affect issues that go through it. Existing "closed" stuff with an empty resolution won't be retro-fixed.

You change your process to a proper sprint/scrum process. If an issue is not "done", the team are not supposed to get any "credit" - the whole point of it is that you measure "done" vs "committed". If it's not done at the end of the sprint, it's not done. That's it. On your specific questions: 1) The data is not wrong -…

Top right hand corner, next to your profile icon. You will only see the cog if you are an admin of one or more projects, and you'll actually need Jira or System admin to get to the custom fields.

Ah, should have hit the line below.

You can no longer get Server trials - it's going away and Atlassian have stopped new licences for it. You should consider a DC or Cloud trial.

It's only a minor confusion, we're just being careful to talk about the right thing. When you start to ask a question on Community, it lists all the systems your Atlassian account has access to, each of which is listed with (Cloud), (Server) or (Data Centre). And options at the end for "none of these, so generic <system> +…

No, it does not. Some people have tried proxying of some forms, but they fail because a human will eventually click on something that uses the actual base url, and the base url is used in all comms with other systems and goes out in email links and so-on. You can't yet customise the Cloud url beyond <your…

The email handlers can't set fields, they're quite simple, only able to process users, subject (summary), body (description) and take a guess at a priority. There are apps which improve on this, and some people have had success with Automations and Scripts scanning "issue just created, look for phrases in the description"

You've tagged this with Cloud, but say you are on Server. Do you have backups of the Server data? Either xml or via the database? To restore issues, you'd need to restore that to a temporary dev system and merge the issue data back into your main production system from it.

Rank is not a number field, but even if it were, it would be of no use in "statistic type" - you can think of the value as being unique for every issue, so all you'd get from a bar chart of it is a flat series of "1 issue has this value". Could you explain what you're trying to achieve here? We might be able to help by…

Nevertheless, it's the correct answer, as there's nothing else we can do to "help", as Trello is not supported by the community. Trello is undergoing some problems, the Statuspage is the best place to watch what Atlassian's Trello people are doing about it, and for direct support, you should go to Trello support (whom, I…

You can monitor the current status of this incident at https://trello.status.atlassian.com

Yes, with "create or comment issues" email-handlers in Jira Core or Software, and with the email channels if you are using Service Management.

https://confluence.atlassian.com/adminjiraserver/getting-started-with-jira-data-center-on-aws-938846966.html is a good guide. Generally there's not much point in migrating Server to AWS any more - it's going away soon, and throwing it on to AWS isn't going to extend its supported lifespan. But the DC guides would enable…

The main point of archiving tasks is to get them out of the searches. So, no.

It depends on the project type. For team-managed projects - no. There's no way to transfer configuration between projects. For company-managed projects - yes, but it's not a migration. Most of the config of a company-managed project is done with global "schemes", so you'll have a field configuration scheme, a permission…

No, there's no way bodge sub-task estimates into your burn-down. Sub-tasks are not items you select for a sprint and commit to, so estimates on them are only relevant as part of an estimate on their parent. Atlassian have not implemented any scheme that looks at the sub-tasks. Even if they did, any such scheme would not…

No, the questions you've seen in the mock are drawn from the same pool as the actual exam (same people wrote them) and Atlassian do not share the questions. Any non-Atlassian source of questions you find are either illegally taken from the pool or were written independently and hence less likely to be representative of the…

You labelled this with Cloud but then said Server in the question. Jira server has an internal API you can use in apps. Both server and Cloud have (similar, but not the same) REST APIs. Whichever one of those three you might be looking for, there's a starting point at https://developer.atlassian.com - select the Cloud or…

Can you check what the resolution is set to, on an issue moved to "done" after you changed and published the workflow?

Um, there's no downvoting on JaC...

See https://confluence.atlassian.com/agile067/velocity-781389935.html and https://confluence.atlassian.com/agile067/viewing-the-version-report-781390346.html

You don't. That data is not held on the issue (and you couldn't store it anyway, you'd have to update every issue every minute) JQL is also a search, it actually says nothing about the format of what you get out of it. A filter result is simply a sorted list of issues that match the JQL. When we look at a filter though,…

That doc is for Server/DC Confluence, a very different thing to Cloud Confluence. The only way to reduce the notifications from Cloud is to get each person to stop watching pages (there is also a request for people to be able to be able to turn off notifications from @mentions)

"now" still matches "updated >= -2w" - in English, that's "updated after 2 weeks ago" You'll need to add an end clause like "updated >= -2w and updated < -1w" For the "over 2 weeks", you'll need another filter, with "updated < -2w"

The "other part" is the create or edit that you are not currently looking at. If you are creating an issue, you do not give it an issue key. If you are creating sub-tasks, you need to give them a pointer to the parent issue they belong to When updating an issue, you have to give it the key of the subtask you are trying to…

Your screenshot is showing a sub-task - first line tells us that where it gives the parent and child issue key - Projects / Versa / Ver-1 / Ver-2