Comments
-
It should be under: settings > backup and restore -> feed it the name of your xml.
-
Yes, you put "conditions" on the transitions to allow only certain groups to use the transitions. You can also use "workflow properties" to block actions (like comment or edit) when an issue is in a particular status in the workflow.
-
No, you need two separate systems. You could do some clever switching if you're only going to be running one at a time, but I wouldn't bother - two installs is far easier. You can replicate the production database and home files to the test system, and no, no new licence - you get a "development licence" with a commercial…
-
I'd use Postgres - it's the one Atlassian develop and test against, but you should use whatever you are best-placed to support from PostGres, MySQL, Oracle and MS-SQL. You don't need to return your renewal - you'll need it for the new server you set up.
-
I'm sorry, I think you're missing the point here - yes, that's a discussion with your manager, and something they pass on to the admin when it's the right time. It is not up to you to arbitrarily remove yourself. Seriously though, where are your back-up admins? If you don't have more than one admin, you have a broken…
-
Next-Gen projects do not yet support sub-tasks.
-
You can't update an issue status with a simple edit action. You need to tell the API to transition the issue through a transition from its current status to the desired one.
-
Yeah, the IDs are well-hidden - they're the ids of objects in the database. If you go to the Admin -> User management -> Groups maintenance piece, and hover over an "edit" or "show users in group" link, you should see a url pop up in the browser, with an "ID" buried in it. However, if you're using an external system for…
-
And what happens when it's still your responsibility? Arbitrarily deciding it's not your problem is not your job, it's your administrator's job. It's irrelevant whether you think you're not part of the project, that is up to the owners of the project.
-
I think it can. I've mostly worked with roles though, and specified the id of the role. If you don't get spaces to work in a group name, I'd try the (numeric) id of the group instead.
-
If a user has no application access, then there is no point adding them to roles and so-on. They are, at most, customers. You can enable email from customers in the email channel settings.
-
Yes, for most project types (it's not there for Next-Gen projects yet, if I understand correctly)
-
You'll have to search for duplicates and close them.
-
Correct, admins need to look after this. What happens if you have stuff assigned to you and/or people need to assign to you and you "leave" on a whim? It breaks the process. The logic is that your admins need to look after that. Where is the back-up admin for the project/system?
-
Yes. But, you have to be using different workflows for each different issue type, and you'll need to edit them a lot. The trick hangs off a "workflow property". If you go into a workflow, edit it, and look at a status, you will find you can add properties. If you add (say) "jira.permission.comment.group = group1" to a…
-
I think you've misunderstood what they're saying there. Your Cloud system will be changed to bring in the new experience. You do not need (or want) to migrate anything.
-
Are you on Cloud or Server?
-
Standard warning - you don't want to "see the Jira data". The database is the worst possible way to look at any Jira data, it's simply not built for any form of reporting. You're going down a bad path here. However, the simple answer to your question is that you're not looking at the Jira database in your db tool there.…
-
Not without code. The screens are based on the issue type, not roles (and it rapidly becomes a mess if you try to do it by role, as things like mandatory and optional still apply by issue type) You could botch something if you have one of the Apps that modifies screen behaviours.
-
Edit the parameters in the setenv.bat file. Be warned though, just throwing more memory at a java process may cause more problems than it solves. I would recommend increasing in small blocks until it becomes stable again - usually 256Kb at a time.
-
You will need someone who is admin of the project to remove you. Project admins can, assuming it's done by role, system and Jira admins can always edit users.
-
It's almost certainly impossible. You can try the h2 editor and see if you can fix each error you get when trying to run Jira in turn, but you are going to lose data doing that, even if it's only a minor corruption Your best option is to look in <jira home>/exports - this is where Jira stores regular backups by default.…
-
Yes, but this is not a good thing to do to your users. You could create a validator for the create issue transition which looks at the drop-down and checks for yes, throwing them back if it is chosen. But, that will annoy them. You're going to find that they either don't raise the item, or they just click the wrong thing…
-
Jira IS a "ticketing system" - people raise issues, other people deal with them and close the issues. With the information you have given us, we can't tell you much more than "create a project, add some users to the right roles, and you have a ticketing system" Please, you'll need to elaborate if you need more than that.
-
Ok, that's readable. You have a broken database. There is a line in your log that says "Caused by: java.lang.IllegalStateException: File corrupted in chunk 253971, " This could be fatal - the h2 database is not suitable for production work, only dev and test, as it can fail without warning (especially with larger data…
-
Could you give us the plain text of the first few lines of that error? It's just small enough that it's not 100% readable. I can make out you've got an SQL error, which suggests a broken database link, but can't make out the rest
-
There's a good step-by-step over at https://community.atlassian.com/t5/Jira-questions/JIRA-Software-project-permission-restrict-user-access-to-one/qaq-p/779572
-
Jira does not have anything resembling "field level security" built into it, you will need to add Apps to do this.
-
Somewhere else - there's no area restricted to administrators other than the actual admin functions. You could have a separate admin-only project that stores stuff (a project of projects), or document things in Confluence - those are the two most popular options we see.
-
I'm afraid this is something one of your administrators has done - you'll need to log in as an admin and change them back, then talk to the admin about being more careful when editing shared settings.