Comments
-
They will stop being visible. The data will still be there in the background, but because you've said "use a screen without the field", you won't see it.
-
Possibly. When you change an issue type scheme, it affects ALL the projects using that scheme. If you are removing issue types, you will have to tell Jira what to move the existing issue types to, because you can't have issues of an invalid type in a project. If you've got different configuration for the new issue type you…
-
Um, you might want to paste that into Botron's issue tracker system if you want urgent help. This is a forum for end-users of Atlassian stuff. Note that there is no attachment here, so you'll need to include whatever is in there too. I'm not saying someone here can't help, but Botron are probably better placed to help you…
-
You'll need some code to do this, but the requirement is unclear. Do you want to validate that the user has put in a due date of +5 days or some other rules (e.g. must be 5 days or greater)? Or simply calculate it with a post-function? I'd do it with the script runner in both cases, but I don't know if you have that…
-
Um, I'm not sure why you are telling us this? It doesn't change the question, or tell us that you are stuck somewhere?
-
Generally, no. However, it MIGHT work in this case, as the database structure does not usually change within point releases. If you open up the 5.2.9 xml and edit the version you find in there to be the same as 5.2.6, then it will *probably* import ok. But there's no way of knowing that and the only real answer is "test it…
-
This looks like one of three things to me: * Validation (*not* conditions) is failing, blocking the transition * It is what it says, someone has changed the status, invalidating the action * A broken transition, probably because of an add-on The reason it is not a condition is simple - the board will ignore any attempt to…
-
It can take some time for a plugin to become enabled after you have enabled it in your my.atlassian account. Give it an hour.
-
Sorry if I came across as grumpy - I've just been through a call where someone did not understand how licences work in Atlassian stuff, and refused to listen. It's quite frustrating, and I should not have reflected that here, as you were not making that mistake!
-
No, that's the role of an agent.
-
This user is not set up as an Agent in that project
-
You don't give licences to users. They become agents (and then consume a licence) when you set them up to be agents in the application management. This user is not set up as an Agent in that project. They are able to comment as they've got some access, but they're not an agent. Check the permissions and roles for the…
-
I'd add a validator to the workflow, but I think you'll need an addon to provide "has work been logged" (or do it with the script runner addon). You won't be able to do this with a simplified workflow either.
-
It will when the trial ends, unless you cancel it.
-
Don't know. You haven't told us what information you're requiring, what a "rework" is, or how you're storing anything in JIRA, or, even, what you're asking!
-
Duplicate of https://answers.atlassian.com/questions/77131/how-can-get-a-report-of-old-unused-user-accounts
-
I don't know of any way to do this, other than creating custom field types that can use the javascript you need.
-
That answer is from 2012. More recent versions of JIRA are preventing the injection of javascript because it breaks things in interesting ways (including introducing security holes). You could try it in the announcement banner, but I'm not sure the code is valid any more, given its age.
-
That leaves a false trail of information about who did things in the system. Which makes it pointless having the accounts.Why can't you do it as yourself? Do it honestly and openly and if questioned why you're doing stuff instead of him, you can say "he's away"
-
Eh? "login as your colleague and then do stuff as yourself" - that's a total waste of time. Login as yourself.Su is an administrators tool, intended for debugging "what a user sees". It should not be used to impersonate other users for updates. (That would be downright illegal in some places)
-
It's for admins. You wouldn't want other users having access because it defeats the whole point of them having accounts.
-
Yes. Don't point it at an existing database.
-
Not really, you'd need to traverse through every single issue, look for their attachments and issue a download command. It would probably be easier to simply go on to the Jira server and take a copy of the "attachments" directory under the Jira Home directory, as that's where Jira keeps them all.
-
You need different issue types if you want different workflows in the same project. Different projects can have different "story" workflows, but the configuration hangs off project and issue type, so you simply can't have different workflows for the same type in the same project.
-
Depends on your version of JIRA Version 6 and lower has both Service Desk and JIRA Agile as add-ons, and you can download them from the archives. In version 7, they're not add-ons any more. It is strongly recommended that you install the applications by using the installation options under "manage applications" If you must…
-
Yeah, I just closed that, sorry.
-
You will need code to do this. I'd usually recommend a listener that picks up a "close" event and scans the sub-tasks and triggers the necessary transitions if they're in the right state. I'm 99% certain that the scripting plugin can be used to construct this process. See…
-
I don't understand the question. The licence has nothing to do with the restoration problems Mark had.
-
From what you've said, it actually sounds like there's something wrong with permissions or disk access to the index directory, but I'm not sure. I'd be tempted to move all the files in the index to a new place and see if you can use the full locking index (because that should always be a valid option)
-
What does the log say is happening? Is it just stopping dead? Could you check the resource usage (E.g. high cpu/memory/disk activity during the first 90%, and then it drops to nothing as it stops, or does one/all of them continue high) It is well worth checking the content of the Jiraissue table though - if that has lots…