Comments
-
Jira Software only supports using Epics as Epics. You can't have others. There are no add-ons that add other types either. The best you can do is add Portfolio to get other similar grouping functions (but they won't be Epics) or the Structure add-on, which allows you more layers in terms of nesting (but still won't use the…
-
Have a read through https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html and https://confluence.atlassian.com/confcloud/migrate-from-confluence-server-to-cloud-724765529.html
-
Jira comes with a load of project templates that help you with generic standardised projects. Log in as an admin and select "create project". You probably want to use a Service Desk project for this. Jira will create the workflows, fields and screens you need for a simple generic ticketing system, all you will need to do…
-
Bother, I was hoping that would contain the smoking gun, but it doesn't. I have seen that error before, several times. Most of the time, the log says what it was, but twice now, it hasn't. A simple restart fixed it once. The other time, we had to get Atlassian support involved. So I'd try restarting, and if the error…
-
There is no password to copy out of a text file. When you install Confluence, it asks you to create an initial admin user, and you give it a password. You need to remember that password to log in after completion.
-
You'd need to be asking about repairs on a postgres forum I'm afraid, this is beyond what I've seen. For the export files though, it is moderately easy. Get a new Jira up and running (make sure it is the same version as the old one), with a single admin user, place the export file into <new jira home>/import and go to…
-
Normal, yes, I get them regularly. Illegal though, at the very least in the EU.
-
No change. You need code provided by add-ons or Behaviours in Script Runner to change the dropdowns (and even these will be ignored in some places). Or you can annoy your users with broken validators (i.e. let them enter data which then gets thrown away because they can't get past validation)
-
Ok, that is a horrible bug in the workflow editor. That screen setting should not be enterable there. It is not used by Jira. Go back to the project admin, look for the "issue type screen scheme" and go into that, check the screen schemes in use match for your current issue type, then go into that and look at what screen…
-
No, you don't. Inactive users do not count towards your licence cap. If you insist on doing this, then you will need to either delete the 20,000 issues, or delete all the comments belonging to your unwanted users then edit the issues where they are the reporter, assignee, or named in any user-picker fields.
-
In my first week. I watched a support person moving an issue through a workflow in a few seconds, giving the team lead all the information he needed so there was no need to struggle through layers of reports or wade through screens of junk like the poor buggers stuck with Remedy. This was well before we had service desk.…
-
We'll need to see more of the atlassian-jira.log Catalina.out is under <jira install>/log
-
Anything that tells us what you're doing. Migrate to another system is functionally useless as anything more than giving us an outline.
-
Because you've configured it to give them admin rights, or installed something to allow them project create. Check the groups in "global permissions" first - who are named as Jira or System admins?
-
If you are on server, then yes, but don't do it. The Jira database is a data store. It is not designed for reporting, even the most simple question like "show me an issue" can result in queries needing hundreds of joins, and it absolutely cannot be updated by systems outside Jira. So, don't. Please use the APIs What are…
-
You need to give it the new licence key. If you've bought a licence this year, then you can get the key for it from my.atlassian.com and paste it into the box you've part redacted
-
You'll need to ask whoever gave you the link for access to it, and to check that it is there.
-
After clicking edit, you can click on the transitions to get more info about them, including the post-functions
-
Update on what? The system burns down on the done column, as it intended to.
-
So, your scripts are putting rubbish in? (Condition about things you row boats with seems to be utterly irrelevant to this question)
-
Not without more information.
-
I would not expect Cloud or Server to go away. They serve very different customer bases. Cloud currently maxes out at 2,000 users. That should increase, but it's never going to reach a level usable for a lot of organisations (the last place I worked had 20,000 users). There is actually no real way to know how many servers…
-
It's in the documentation - wherever you put the home directory on install needs to be copied to your safe backup place.
-
Yes, do NOT even think about doing this with SQL. For very simple configurations it can work, but as soon as you have more than one workflow or use different fields, you can easily and rapidly corrupt your data beyond repair. Edit the issue type schemes for the projects, this will take you through a safe migration that…
-
No, Jira does not reuse numbers.
-
Don't put bad data into the fields. It's going to be bad stuff in a text or label field. To identify which one, please read the log, as the error suggests. Or read the data. The usual culprit is someone pasting in control characters or emojis copied in from an email or document.
-
A video won't help you, as it will be of a specific version and configured differently to yours, so it will all look different. The document Christian pointed you too is more generic and better at covering all possible configurations.
-
Probably need to see the whole error, as this is just the top part of the message
-
Some setups expose it in the footer, but if you're not on one of those, then ask your admins what version it is.
-
No, just be 100% sure you want them gone, as it's a nightmare to get them back from backups.