Nic Brough -Adaptavist- Expert

Could you please read what I've said before properly? And stop misrepresenting it in your own words too. Your last comment totally misrepresents what I've said and I want it to be clear that it is your misreading that is the problem. And you still have not answered the question: Why is it a good thing to let people do…

This does not answer the question. Your car analogy is wrong - taking cars away is not what is being done here. Do we not have laws that try to stop people doing stupid things like crashing? And safety features? Same with electricity - have a look at a plug socket - can you insert any conductive object you want into it so…

Could you tell us more about where this happens? What are you doing when you get it and what data entry is provoking it?

Yes, with a theme or an app that can re-arrange things. Or even hacking the core code, but I cannot recommend that.

The product has basic functionality otherwise it wouldn't be there. I don't understand why you think I'm crazy? Please could you answer the question I've asked several times? How is it a good thing to let people do stupid things, make a mess and then have to pay other people to clean up when they could be off doing more…

This means that the process running Jira does not have access to the index files and directory. This usually happens when the wrong user runs Jira, takes ownership of some of the files and directories, and then it is restarted with another user who now cannot read or write to them. Stop Jira, correct the ownership of…

Nope, nope, nope. It doesn't make any sense to let people break things in ways that are known to be not useful. It's a complete waste of their time, plus the time of the people who then have to fix it. I have been one of those having to fix stupid things like this for a very long time. It's boring, expensive and dull. Not…

Jira doesn't have any code in it to read .msg files. You could look for an app that can do it, or code one yourself, but plain Jira just doesn't have a way to read them.

Jira and Confluence are totally separate systems, so I think you need to explain what you are thinking by "take Jira out of Confluence"?

The stuff you see in a burndown chart is all calculated from the issues and sprint data. So you'll need to fetch that over the REST interface and put together some code to replicate the calculations the chart is doing.

The paid add-ons all shift their support to other people who are willing to take the risk, or explicitly state that they will not support the breakages that people do. I'm not averse to this - I've been very well paid for fixing those when they go wrong. I don't understand why you think "don't give people the rope to hang…

No, we can't see what has happened. We have no access to your systems, nor any knowledge of what you are using that has let someone seemingly attack you. All we can help you with is ruling out Atlassian software as an attack vector. I don't understand why you've been struggling to deal with something for six months and…

Cloud does not have any function that would do this, nor does it allow for apps to do it (Cloud does not support the functions that Behaviours injects, otherwise we would have written Behaviours for Cloud into SR for Cloud a long time ago.)

Change the "field configuration scheme" for the project - you can set component and label as mandatory in there. Defaulting a label is not possible (and kind of defeats the purpose of what they're for anyway)

Crowd is not an LDAP server, it does not have any functionality that would make it look like one.

The SSL certificate your call is presenting to the server is not valid. You will need to change to a valid certificate.

None of this appears to have anything to do with Atlassian. I think you're asking in completely the wrong place. It sounds like you have installed something that allows malicious people to do bad things on your machine. Atlassian software does not have those functions, so I think you should be looking to security forums…

That's not true, if you break something with a dodgy script a lot of people will go to support, which then means you ARE affecting others. Plus of course, you've broken things for all of your users, not just the person getting the script wrong. If I offered a support service, I would turn off the ability for people to…

Nothing from what you've said. I would want to closely check that you really do have a field configuration scheme that says to use two separate field configurations for Story and Default, in this project. I can't find a way to replicate this issue unless I'm sharing the field configurations across all issue types.

Look to the three dots to the upper-right of the issue view - there is a "move" option in there that takes you to a screen with "change project" and "change parent" options. Note that the "change parent" will only appear if the issue is a sub-task, it's not for changing the Epic links.

No, you need to move to apps that provide the same functionality on Cloud. Some apps can take data from their server version to their Cloud version, but that is entirely a function of the app, it's not something you can generically code for.

Confluence does not have a SOAP interface any more, you'll need to use REST. But yes, you can copy your data up to Confluence with some scripting/coding.

No, the view of organisations has no restriction functions - any agent can see all the organisations.

You're pretty close, just one more thing to add to your code. The line issue.getCustomFieldValue(com.atlassian.jira.component.ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Testing Group")) is getting a list of groups selected in the field, and the items on the list are group objects, not strings.…

This sort of reporting should not be done with database access. The database is not in the slightest bit suitable for reporting, and building a report, even a simple one like you've shown here, is a nightmare. The SQL for your report needs 21 joins and a load more if anyone has logged more work, plus you'll need to do some…

You will need to upgrade to a version that the migration assistant works for, or use an export/import via CSV which will lose you a lot of data.

Jira is not a monitoring system, it is an issue tracker. Jira is the wrong place to monitor stuff, but it can well be the right place to report that something unexpected happened. Have a look at your monitoring tool, it can detect problems, but how it announces them is a bit harder - could it poke them into Jira? (Whatever…

I am sorry that we cannot tell you much, but there is no context for your question. I guess that the prior comments might help our understanding, but you have asked a question that does not have any of that history. We don't know what "prior comments" you are asking about. The best I can do is suggest that you click on…

That is very odd and I do not know what is wrong. I installed 8.13 this morning and went through most of what you saw, but at 2:28, that "you'll need an atlassian account" stuff appeared as part of a screen that had a box for licence entry and another with the server id in it. It wasn't the whole of the screen, as you are…

Ok, I'm stuck too - I just created a project, added an issue, deleted the project, then tried to create a new one with the same name and key - it stopped me when the key was the same as the old one, but not the name. I think we might need to ask Atlassian about this one.