Nic Brough -Adaptavist- Expert

Ahh, you have an export that's slightly broken. Start from Ana's fix over at https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-reserved-refs-when-cleaning-up-with-BFG-tool/qaq-p/702969

>Numbering will be for developers to know which ticket they need to finish first But they should be finishing the issues assigned to them that are not done. And if/when they finish all of those, then they go to the board and pick the one at the top of the to-do column. You don't need numbering or ordering or rules. Just…

The content and order of issues on a board is determined by the board filter, not the various sub-slicing/drill-down options you can do later. Swimlanes (and quick filters) define sub-sets of the board issues, but inherit the sort order defined by the board. They're part of the board and showing a sub-set of it, so it…

Between us, we do have a lot of MySQL experience, but we're mostly here to talk Atlassian, and a lost MySQL database is a bit off-topic. Some of us may well have run into this (whether it was an Atlassian database or something else), but it is not the focus of what most people are here for. I responded because you had been…

This is something I'd like in Jira as well - a reminder "scratchpad" type thing. Don't get me wrong - Jira does not have anything remotely like this, and there's a "metric shed-load" of other programs that do it. And they do it really well. Except that they just do "scratchpad" and all fail to get my jottings to anywhere…

Um, I used it last week, it does work.

I'm afraid your belief is contradicted by the code. It is absolutely not a "small change".

Why are you dictating reporting to teams that are supposed to be self-organising?

I would shorten this a bit, to simplify it. The first line I would change is if(issue.getCustomFieldValue(cfm.getCustomFieldObjectByName("LCL RG Points"))!=null) { score9Field = (double)issue.getCustomFieldValue(cfm.getCustomFieldObjectByName("LCL RG Points"))} Leave out the "else", as you can just leave the score9Field as…

You can't number the issues themselves. Not because you can't physically do it, but because it is not really of any use. * As soon as the board changes, you would have to re-number every issue. * And somehow store different numbers for each and every board. * And tell people what the different numbers need and somehow know…

The "changed by" function does not yet support Summary or Description. Have a run through https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/ to see if there are other functions that might get you closer.

Ahh, I see. Export from queue would be a useful feature, and not a hard one to implement (as a queue is already a search!), and I'm sure I've seen a request for it. Shame it's not there yet.

There is no way to do that. There is an open request to be able to configure the robots file for your site, but that is a request for an engine not to index you and won't stop it if the engine feels like it. See https://jira.atlassian.com/browse/CLOUD-5915

Erm. " requires the QA person to know if there is UAT testing and will show 2 buttons they must choose from: UAT and Ready to release. They may not know the correct answer" If they don't know the correct answer, then they can't fill in the field either.

Edit the workflows. Your admins will have to do that. Part of their job is to help you work in the best way you can, but another part is also to prevent a mess being made by people demanding to do randomly complex and inefficient things. If you want changes, sometimes you'll need to take them to the company to justify why…

Numbering issues would have to be done by going from top to bottom through each row and column. The numbers wouldn't tell you anything more than where the card is on the board, which is what the board is already showing you. The next ticket to tackle is the one at the top of the column that no-one else is working on.

What does the Teams docs think a "Jira ID" is? Jira is absolutely riddled with IDs, almost every table has one that means something different. We can't tell you where to look for a "Jira ID" without an explanation of what you think it is.

So where is that message coming from? It's not a native Jira message.

Actually, it's pretty much the same for Server. Go to Issues -> Search, and run a search for the issues you want. Then use the tools menu near the top to get to "export". Select the settings you want and it'll dump it out to CSV, which spreadsheets can read.

Any system can talk to Jira over its REST API - see https://developer.atlassian.com/cloud/jira/platform/rest/v3/

What do you mean by "sync"? I assume you have a Jira system somewhere, what are you trying to do with it and oracle support? 

There's not enough of the error log here to tell us much. Although there's clearly a problem with your LDAP connection which needs fixing.

Ok, so what code have you added to generate the "please provide a valid value" message?

Ok, I think you are misunderstanding the issue/sub-task relation. An issue type can not have sub-tasks. They're not issues, they are an attribute of an issue. Only an issue can have sub-tasks. You appear to be trying to attach a sub-task to an issue type. Where you're using issue: 10002, that's probably an existing issue…

Nor do we, without you telling us what you are asking about. Could you explain your question? Bear in mind we are a community of people involved with Atlassian, so if it's outside that ecosystem, you are probably yelling in the wrong place. And please STOP SHOUTING. It is hard to read, and many find it rude.

Ok, so those 76 will vanish from the backlog when you end the sprint because they are done. The rest will remain in the backlog because the are not done, and the board is selecting for them.

DO NOT DO THIS. You must not rename Epic in Jira Software. By all means use Portfolio, Big-Picture, Structure, whatever, to create more layers, but do not rename Epic. You will cause untold problems. Atlassian are working on a way to change this, so it can be renamed without problems, as part of bringing it in line with…

I'm afraid you've had no answer here because this isn't really an Atlassian question. Something has broken in your MySQL upgrade and you seem to have lost a database. I've always run from database dumps, so when I've had errors like this before, I've been able to restore from them. I don't know much else about recovering…

Jira has no functionality that can do this. I'm not aware of anything that can enable it either.

No, transition screens are always presented to the user. You could use parallel transitions though - let's say you have a field called "my field", which you want to be mandatory when going from status X to Y Create two transitions from X to Y, with * Transition 1: * Condition: my-field is empty * Transition screen: a…