Nic Brough -Adaptavist- Expert

The short and brutal answer to this is that your WAF rule is inadequate. Confluence searches are done in CQL (well, the "advanced" ones anyway), which does look a bit like SQL, so I understand the failings of the more primitive injection protection methods there - they're throwing false positives based on plain input…

<cough>, I suspect it is a "quiet majority", not a "vocal minority". And yes, people get vocal when they see unwanted change, but you have to balance that against the number who do not complain, and look at how the complaints are formed too, to get a good feel for it. (by "how", I mean the tone - are they howling "put it…

OK, I'm stuck, I've only ever seen that either throw errors into the logs, or happen with external user directories. I think this one probably needs to go to Atlassian support!

Ok, so if I were to do this from scratch, I would * Choose my field that I want to protect. Let's call it "Pet-type" * Create four new screens (making liberal use of copy), with names and content such as: * Screen-c: Has all the fields I want the users to give me when creating an issue (maybe including pet-type) *…

I'd want to look for "tuser", but if there are no errors in the log at that point, I wouldn't worry about it. What type of user directory is it? Internal? External LDAP/Crowd/something?

Ok, but that has nothing to do with what you asked. You're right, of course, action 1 is the transition from <nothing there> to "initial status", but not only can you change the name of that step, you can change it to point elsewhere.

Ok, can you get access to the logs? See what happens in <jira home>/log/atlassian-jira.log when you click "update" on that screen

There's no record of change in embedded crowd. How are you changing the email?

That's a very different thing from knowing what the starting status in the workflow is. At your point in the process, you've got an existing issue and are in the middle of a transition, so there is a step, and hence status, behind you. In fact, the issue is still in the "previous" status until the "change status" post…

No, you can't share the lists. The whole point of the cascading select is that the items on the second list vary by parent and that they are always separate options.

No, because your data has effectively branched, and there is no way to merge it back without a huge project (which will incur significant downtime)

You could add a custom field that allows selection of a "sub-type", but it won't do anything with the request or issue type other than be another data field.

It sounds like you'd installed it as a service, so it kept running, even on restart.

Have a look at the table - the field names are clear (mostly)

It is not "trying to link wf2 to wf1", it is trying to migrate the data. Imagine you currently have a single workflow in your scheme mapped to all issues by default (or even explicitly saying Bug: wf1, and Feature: wf1) wf1: Open -> in progress -> done Now imagine you create 6 issues, three Bugs, and three Feautures,…

The applications only store their data on their local file systems (that may well be shared, yes, but I doubt your personal machine is part of that share!) The folder you have found is from an installation of Confluence on your local machine. Unless you are running a Confluence service from your machine, you won't need it.…

I have a feeling it's a quirk of the billing system - you sign up for an Atlassian system, it goes into trial mode, and then you pay for it if you want to keep it. But when it's free, you don't need to pay. But I don't think the licence system understands that, it assumes you're going to. I remember seeing this when I got…

I have a feeling it's a quirk of billing - you sign up for an Atlassian system, it goes into trial mode, and then you pay for it if you want to keep it. But when it's free, you don't need to pay. But I don't think the licence system understands that, it assumes you're going to. I remember seeing this when I got my free…

My guess is it's been turned off for now - there's a lot of noise from people who really really do not want it. I think you might be the first person I've seen like it (I'm in the middle - I do not like it, but if it can be turned off for me, I'm happy)

Your plugin will need some code that can push the data out into your remote database. Typically, that will need a database driver for the remote database to be available.

I would strongly recommend that you stop reading the database, it's the single worst way you can possibly get data out of Jira. If you insist on doing this badly, I'll save you some time - it's on jiraissue, but you won't like the way it handles. I'd strongly recommend using the REST API for whatever you're doing instead.

I do not understand the question. The point of the cascading select list is that it has two levels to be displayed, so it does. Could you illustrate with a screen shot and description of what you'd like changed in it?

Correct, you can create issues that you then cannot see because of the security level. It can't stop you creating the issue, just hides it.

Note that is Server only, it does not work on Cloud, which the post was about.

The answer above is entirely correct. Your fix for when you imported your data into the wrong column is a good fix, but it's not doing any remapping, it's reconfiguring the project to not have "done" and then re-adding it.

Your "workaround" is "do it by hand", or to use an identity system that supports it. The reason Scriptrunner cannot do this is as Kristian said - Cloud has no available API for this. Other apps or scripts will have precisely the same problem - there is no call they can make to do this.

That is not the "exact cause", there's a whole load of related error messages around that which might tell you a lot more. Could you look at the application log instead? I'd like to see what Confluence is trying to do as it starts up, so look to <confluence home>/log/atlassian-confluence.log (ideally, stop all confluence…

The Apache log is just telling you it can't connect to a service, presumably Confluence. From the one line of log you have given us, we can't even tell which log that was in, and it's certainly not a pointer to a crash. Could you give us the application log content at the time of the shutdown/crash please? Unless you read…

If their emails are not being imported, but other people's are, then there is either an error in processing them (which would give you errors in Jira), or they are not reaching that mailbox. Could you get them to send the most simple email possible? Plain text, with something like just "hello" in the subject and "test" -…

That does not describe what you are trying to do in enough detail. It's got a couple of pointers to things you might be editing and a class of error message. Maybe it would be easier if you told us what documentation you are following and what you are doing differently to what it says?