Comments
-
Cloud is run by atlassian for you, you sign up and it works. It has some restrictions in flexibility, but most users are fine with them. Server you download, install and run on your own hardware, and you then need resources to look after that.
-
Possibly, but go back to the original error and work through the lines in that to find the cause.
-
A null pointer exception is not a helpful error message in java, it's the fallback that really doesn't mean much more than "something has gone wrong". You need to look at all of the error message. You can ignore most of the lines in the error, they are for coders, giving the lines of java they'd need to look at, but we do…
-
What are the changes and what does the notification scheme say?
-
There's a significant difference between "adding a field" and "adding a label or other custom field value". You don't mean "they need admin permission to add a field", you really mean that the user can't use quick edit. 1. Actually, they can. Click edit, you will be offered all fields on the edit screen, whether they have…
-
I was hoping for Summit time :-) But thanks for the update.
-
This isn't the place to get comments from Atlassian - we're end users like you, not Atlassian.
-
No, the licence bands are currently 100 or 500. I understand that 250 is on the way (the experts and partners have been told), but I don't know the date or details.
-
You can not. OnDemand does not allow for customisation of code (and also has a limited set of addons you can install). Your choices are: * Move to self-hosted * Move to a host who will allow code changes like this * Find/raise a feature request for OnDemand customisations to the dashboard and wait for them to be…
-
Go to the list of workflows, find the duff one under the list of "inactive" workflows, and click "delete" to the right of it. (If it's under "active" workflows, then you're using it and you'll need to swap the projects using it to a different scheme)
-
See https://confluence.atlassian.com/adminjiraserver070/enabling-public-signup-and-captcha-749382800.html
-
Remove the labels from all the issues you've put them on.
-
I'm afraid the community licences are for single production instances. You might ask for a second community licence though.
-
If you have a full licence, then yes. You need one full licence per PRODUCTION server, but it comes with a *development* licence you can use for dev/test instances, as well as cold standby servers. Look in your my.atlassian account under the actual licence keys for a link to generate the dev licence.
-
That's not on the page you think you want to edit. Try https://developer.atlassian.com/display/JIRADEV/Customizing+Text
-
That usually means your SSL certificates are incorrect, or you're using the wrong certificate authority or type. Check all the cert settings!
-
No, you have nothing to worry about here - just restore the backup (while the applications are down of course)
-
I'd say something has changed in the datbase permissions, OR you've started using a function that uses active objects that you weren't using before. You really should grant the Jira user "create table" rights in the database and try it again.
-
The error is pretty clear - Jira needs to create tables for Active Objects, and the database account you have configured it with does not have the required rights to create the tables in the database. Correct the permissions in the database and try it again.
-
Sorry, Jira, Confluence and the rest all have the same licence model.Once your licence expires, you will not be able to upgrade to a version released after the date of expiry. You can renew after a licence lapse, but if it's been over a year, you'll simply need a new licence.
-
Nothing. Your licence lets you use any version of JIRA released before the end of the licence.
-
Yes.
-
Go back to the workflow view and find the arrow(s) going into the "done" status. One of them will be the global transition, and you should be able to click on that to get the transition settings.
-
That's an error happening because you are trying to add another transition to a step in a workflow when you already have one. Nothing to do with screens. If you want a screen to pop up during the transition (i.e. when moving to "done", I want to ask the user to update the "versions" field), then you need to amend the…
-
Could you expand on "trying to display a screen after an issue transition"? When you complete a transition in JIRA you land on the issue view, or the screen you were on when you triggered the transition, so adding another screen doesn't make a lot of sense.
-
See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
Also bear in mind that Cloud is different again - broadly, your admins are just JIRA Admins, but with some other options removed.
-
The list is at https://confluence.atlassian.com/jira/managing-global-permissions-185729559.html#ManagingGlobalPermissions-About%27JIRASystemAdministrators%27and%27JIRAAdministrators%27
-
So what did you map the "closed" status to?
-
Look at the workflow for the project you are importing into - does that have a status of "closed" in it? How did you map the data when you ran through the import configuration?