Comments
-
Add "and issuetype in standardIssueTypes()" to your filters.
-
Do you have create, move and edit permission in both the source and target projects? (I say "Projects" to cover the assumption that you're trying to move from one project to another with this move)
-
What does the log say? Is it running?
-
The linking function you are looking for only works internally on a single integrated system. You have installed two Jira systems - one Core and one Core + SD. You'll get the links you are looking for if you simply get rid of the unnecessary Core install and use the Core + SD one for everything.
-
Set up Incident, Problem and Change request types and map them to the issue types.
-
"labelled as done" is irrelevant to the strike-out function. An issue's display will take on the strike-out (in many places) when the resolution is set to a value. When the resolution says "unresolved", it is a display for us telling us "the field is empty", and it won't get struck out. An issue's status, what column it is…
-
No, you'll need to drop all the tables on each new run. But you can use the same database over and over.
-
For older versions of Jira, yes, it was a disaster. Both of them would be unable to write issues correctly and their indexes fail rapidly. If you left them long enough, with active users, you'd get a completely corrupt database. Newer versions of Jira try to prevent the corruption - the first one to connect writes a record…
-
No. A user can either move an issue or they can't. You can't restrict what status they choose if the workflows are different.
-
Have a look through https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html - it goes into more detail than I can type quickly.
-
That looks right to me. You upload the zipped file when you tell Cloud to restore the files.
-
You can't do that on Cloud, Dave is talking about the server side.
-
You need to set up the Tomcat connector to talk to Apache as well.
-
254 characters for text and then whatever your database can handle in a large object column (i.e far more text than is generally useful in a field)
-
The password reset docs apply for all versions of 6 (and quite a long way back into v5 if memory serves)
-
See https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html
-
It's an "estimate" template.
-
To use the CLI, you have to have a working, running Confluence for it to talk to. I don't think you've got one of those, and it does look like you need to go to a backup. Although the recovery tool might be able to get you working again with some data loss.
-
You'll need to remove the any logged in user from the scheme and replace it with something to let the right users back into it.
-
I suspect writing an add-on to provide your own field is the only option.
-
As long as your admins let them.
-
I'm afraid it's not "quite different". Once a new user is created, they are an existing user. The age of their account is irrelevant. So you need to hide new projects from all users and then grant the access to the limited few.
-
Forget the playsql add-on, it's irrelevant to the start up of Confluence, as is the application link. Both of these are things that Confluence looks at later in the start up and it's failing before it gets to them. You are not getting a response when you browse to Confluence because it's not able to complete the start up.…
-
Correct, you need to do what the other posts you've found say - re-build your access, removing "any logged in user" from permissions.
-
1. See https://confluence.atlassian.com/adminjiraserver074/configuring-jira-service-desk-approvals-881683849.html 2. Go to admin -> issue types and click "add"
-
Yes, you edit the workflow. You should choose one of the two options - doing both is confusing for the users because they'll choose a resolution only to have it overridden by the post-function.
-
You will need to move your whole installation to data centre licences. Jira Service Desk and Software are both applications that are installed on a Jira Core, so to upgrade them to data centre, you need to upgrade the core they run on, You can keep all of your current configuration, you only need to apply the licence to…
-
There's no field for hh:mm like that, as far as I can tell from the marketplace.
-
You'll need to explain what a "database information" field is. What add-on provides it?
-
What makes you think it's caching causing the problem?