Comments
-
The fields, schemes, issue types, priorities, resolutions, screens and so-on all fall into "global config". If you delete a project, you won't affect them. Except for field content, which will be deleted along with the issues holding it.
-
Service Desk, or plain Core or Software?
-
What does the log say the problem is? Can you check the exact compatibilities between your databases and versions?
-
The database connection is not configured quite right. Start at https://confluence.atlassian.com/jirakb/invalid-state-the-connection-object-is-closed-due-to-connection-closure-153748854.html
-
Again, I can't see a problem - I see field names and selects. The placement looks wrong though. Do you have Behaviours, 3rd party custom fields, or any javascript tricks in play?
-
You're probably going quicker than you think - it was a steep learning curve when I started with Jira, and that was when we had 1/5 the functionality you've got nowadays!
-
Er, you're expected to not badly design your workflow, not botch fixes in later.
-
The problem for most of us here is that simply following the docs is good enough for almost all of us. What sort of errors are you running into ?
-
Oops. See https://confluence.atlassian.com/confkb/unknown-column-error-when-upgrading-from-confluence-5-x-to-newer-versions-915476193.html
-
Looks to me like it's already running. Check what is really running with ps -ef
-
Indeed, that's the point of a burndown - it's not done until it really is done. A burndown that "is a better reflection of progress" is not a burndown chart and is useless for Sprint/Scrum.
-
JQL (filtering) and reporting are two separate things. JQL / filters find issues. That's it. They have nothing to say about how they are displayed or reported on. That's up to the reports you use them in. You can easily filter for "issues per month", because you can use things like "created > startofmonth(x) and created <…
-
I don't know how else to put this, but you plainly have not tried it. When you search, using that example, for "project = x", you get all the issues. (If there are more than 1,000, you will need to consider paging, or take a proper look at the real reason why you're doing this)
-
Sharepoint is [where documents go to die ^H^H^H], a document repository, not an issue tracker, so an explanation in those terms is not likely to help you much, as they're not analogous. The easiest thing to do is think of a Jira project as a "Container for issues". The container holds as many issues as you care to…
-
Tell them to start with a project search - see https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#searching-for-issues-examples
-
I am sorry, I am still not clear. Is this about email coming in to, or going out from, Service Desk?
-
Jira has no code that makes sub-tasks specific to parent types at all. If you can create a sub-task in a project, you can create any type under any type of parent. You'll need to think about code to do this - specifically a validator which can block the user from creating the "wrong" type of issue.
-
Probably mismatched keys.
-
You can't. Your only option is to migrate to server (or hope that Atlassian give up and re-build a different interface)
-
Simple answer - use the REST APIs on both servers. A better answer might be to use one of the Synchronisation add-ons (Backbone, Exalate etc) to duplicate projects between the two servers. But I'd start with the easy question - why not merge them? (There's good reasons why not, which are all fine, but I have to ask,…
-
Have a look at the options for the environment field in the list of custom fields, I suspect you will find that you don't have a value with key 10905 on it.
-
Nope. It's optional in the field config. Have another read of the question - the first sentence is correct (still - you're posting on a 6 year old question!).
-
Yes, an update of a script will overwrite the old script. That will happen for each field, independently. If that is not the case, could you tell us what version of Jira and ScriptRunner you have?
-
Please read the documentation given. It will take you where you need to go if you read it.
-
Check the project permission scheme, and look at the line for "Browse project". This will probably say something like "Role: Users". Now go to the users/people section in the project admin, and remove all the groups and users from the Role of Users. Then add your 5 users into the role. Note that if you have other rules…
-
Annoyingly, there is no direct link to find admins in Jira (unlike Confluence), I'm afraid you will have to ask the other users.
-
You'll need to ask your administrators for admin access if you want to add fields. However, a good administrator team will tend to limit that, as admin access should always be limited to the admin team.
-
It's not a bug, you have misconfigured the file system. The user running the Jira service does not have the right access to the installation and/or home directories. Stop Jira, make sure both directories are owned by the user that Jira will run as, and that it has full access to them (and all sub-directories) and restart…
-
Are the sub-tasks in the far right-hand column of the board? And are all the subtasks visible to the user?
-
Ok, have a close look at what you've got it called in your system - it's labelS by default.