Comments
-
No, the whole point of the daily backup is that it backs up the whole system. If you want to drop certain spaces out, you'll need to do some coding to enable a blacklist of data to be ignored during export. Obviously, if you do this, you'll loose all your test data if anything ever goes wrong
-
You need to be a project administrator, then you can maintain them for that project. See https://confluence.atlassian.com/display/JIRA/Defining+a+Component
-
The symptoms you are seeing are suggesting a slow network connection. It might be a compound - network heavy "bad" javascript on the client side making heavy/frequent requests over a slow network. The way to work this out is to monitor the server side. You've looked at the database already, and I'd agree with you…
-
You'll need to pull it out of a recent backup and merge it back in. This is one reason most admins simply remove all "delete issue" permissions.
-
The base url is always available in JIRA, whereever you are working. Your "accessing" url should NEVER be different from that - JIRA has no awareness of external urls, and it can't. You need to use the base url.
-
You need to use the same base url as accessing url.
-
Your Crowd system is set up to authenticate you against another directory, probably some form of LDAP. It has not been given write access to the directory, so it cannot change your password. You will need to contact your directory administrators and get your password changed in that directory.
-
Ok, there's some form of substitution happening here, it's either an obscure Tomcat thing, or someone has scripted something, or they've hacked a template. I'm afraid you probably need to go back to the "modified files" and go over *anything* that has been changed. Also, are you using any language with odd characters?
-
Hmm. Is it just 5 coming out as #5 5 too? I mean if you enter "575" do you get "#5 57#5 5"?
-
Ok, that's good. (Well, not good, but at least it is consistently related to number fields)I'm not sure I can work out how to replicate it though. The fact it comes out in both the UI display and the exports, assuming by "export" you mean you are using a spreadsheet or word-processing download, implies that there is some…
-
I assume you're talking about a field - could you explain what type of field it is?
-
Hmm, my guess is that your Java locale is set to something unusual - the ? are indicating "I can't read this character", which is not something the cleaner should have output.
-
I'd take a look at the input and output - what has the cleaner done? Is the input even valid?
-
I'd take a look at the entities.xml again - it's nearly doubled in size, which suggests something is very wrong.
-
Did you repack the corrected files into the import.zip with the right name? (I ask because that's the step I always forget) Can you also check that your data in the entities.xml looks ok?
-
The zip of the attachments is used in the next step, in the Import to JIRA Cloud section. The error you are seeing is not uncommon, it's because databases aren't all quite equal. You can fix it and retry the upload with https://confluence.atlassian.com/jira/removing-invalid-characters-from-xml-backups-12079.html
-
Mmm, CSV isn't going to cut it for that, you're going to need to think about converting your data to Jira's import XML, or writing Jelly scripts to do it. Or another format that Jira can import from
-
Getting started is written up at https://confluence.atlassian.com/display/JIRA/JIRA+User's+Guide
-
Not in the way you're thinking. JIRA normally has a really simple user system - you are either a user, or you are not. Most addons, including Capture, follow that - if you want to use Capture, you have to be a JIRA user. Service Desk adds two more types of user - Agents and Customers. Agents are also JIRA users, but…
-
There are some directives and javascript tricks you can inject into pages that ask the user's browser to not allow downloads. But I'm afraid that behind the scenes, "view" is the same as "download". If you want a user to see something in their client, you have to give them the data for the browser to render. Which means…
-
That is a post-function, not a listener. I'm not sure why you are wandering off to do other things, when I specifically said "listener". Now, a post-function could do the job, but I've suggested a listener because you want to do things when editing as well, and there are no post-functions there. And, on your last comment,…
-
Start at https://scriptrunner.adaptavist.com/4.3.5/jira/listeners.html for getting a listener up.
-
Again, Behaviours will not help you. It acts on the screen, and your users will only have the field there in certain cases, so it's not going to do anything. That doesn't look like listener code. There's no forms in listeners.
-
you need a scripted listener that will listen out for any issue update where a user might set the customer field, read the change and then set the new security level as appropriate.
-
It won't work with a Behaviour because only people who are part of a security level can set it. You had roughly the right idea, but you need a scripted listener that will listen out for any issue update where a user might set the customer field, read the change and then set the new security level as appropriate.
-
That looks like a front-end script of some sort. It's not going to work, you need to set it in the back end, as a post-function.
-
You will need to find/write code that can set the security level when your field is set.
-
Your field has nothing to do with the security level.
-
Ah, ok. Remember that if a user cannot see an issue (because of the project permissions or the security level), then it is NOT reported to them in any way. A simple example: You have the security example I wrote up before. You've got a project with 15 issues, 1 with no security level, 2 with A, 4 with B and 8 with C. You…
-
What's the difference between the issues you can see the level on and the ones you can't? Different security levels?