Comments
-
No. You'll have an installation of JIRA on a server. You will be running Service Desk and Software within that single server. You don't need application links - the applications are all running inside a single JIRA Server.
-
Yes. Install one of them, then go to Admin -> Manage applications and add the other. Generally, we've found it easiest to install JIRA Software from scratch and add Service Desk, but you can do it the other way around (or even install Core and then add the both)
-
Ok, you'll need to find or write some code to do that sort of calculation for you. I'd probably lean towards a scripted field, which would be automatic, and reportable.
-
It clarifies that you're happy to have independent, arbitrary and subjective KPIs measured (So I would very strongly caution you against reporting on them on any level outside each separate project. As what one project is measuring simply cannot be compared with another) The diagram doesn't help though. 50% of what?
-
This is a specification which looks ok on the surface, but is really far too vague to usefully build. A key performance indicator needs a clear definition. Things like "the percentage of calls resolved within 2 hours of initial contact" or "the average monetary cost of a support call" or "up time of a service" are defined…
-
Same answer as before.
-
* As per the first paragraph in my answer * As per the second paragraph in my answer We can't tell you what might change in your system - we don't know what you've configured, what add-ons you're using and so-on. It's something you need to work out for yourself.
-
Your data will be upgraded, including all the custom fields, users and configurations. For details of the changes, there's no way we can tell you about the "risks" or even what might affect you directly. You should read the release notes for each major release of JIRA between 6.3 and the version you want to land on. (i.e.…
-
Yes and no. JIRA Core is an application. JIRA Service Desk is an application that can be added to JIRA Core. It's also available as a bundled installation, which saves the hassle of installing the application if you are starting clean. If you're on Cloud, then you don't need to worry about installation, you just go to your…
-
That sort of processing is exactly what JIRA is for - a distinct workflow, simple fields etc.
-
That is a long way away from what Confluence is for. For some basic elements of it, there are some options, but the process you've got there really does need something with a proper generalised workflow engine. Obviously, I'm going to recommend that you try JIRA. Probably with Service Desk
-
That's nothing to do with your original question. The layout of fields on screen is nothing to do with their option content. You'll need to amend code to re-arrange the screen to get another field on the same line as assignee. If you meant you want a field the same as assignee, but not assignee, then please re-read the…
-
Not for a custom field - the possible combinations of what you might want in there are far too vast to code for. If you use the reporter or assignee field though, you have complete control over them, because they have clear rules. The reporter field is limited to "people who can create an issue" and the assignee list is…
-
You'll need some coding to do that. There are some plugins available that might help you, but you need to think carefully about what you mean by "all users that are part of the project" Also, you've said you're using OnDemand, so you can't install plugins or code... (yet)
-
That query looks good to me. I'm not actually sure of the effects on the field config and context because it's not a standard custom field. I suspect they'll actually be fine, but I'd want to check and test it before relying on my instinct.
-
Ah, sorry, I misread it and got the context wrong. Didn't realise it was the Software ranking field. No, that does not get cleared, so, in theory, yes, you could replace the custom field entry. But you'll need to check the field configurations and contexts are added back correctly as well, and, as usual, reindex the whole…
-
No, the issue content goes as well. I'd take a backup before you do this.
-
It does answer the question, it tells you how to set up the service desk. If you look to the left of the page, the documentation tree contains a reference to installing your service desk - I suspect that's what you are looking for.
-
Not with HSQL - that can fail spectacularly. Anyway, if the plain copy has not worked because your HSQL database is trashed, your only real hope is what Fabio said about backups.
-
Possibly. It depends mainly on what the database was. If you were using a proper database, then you should be able to install a new Jira 4.2, copy the home directory, and point it at the database. If, however, you were using the built-in HSQL, then the good news is "yes, you can simply copy the home directory". The bad…
-
Hmm. Ok, so your LDAP doesn't match your SSO. That could be interesting. However, start with the LDAP. Are you 100% sure that the LDAP account you are using is valid? Can you log into other LDAP connected systems with that username and password?
-
Ok. Did you have Confluence offline when you did the SQL change? Also, what authentication method are you using? Internal? Crowd, LDAP etc? And finally, what does your log say when you try to log in?
-
Oh, heck, no, you can't do this. You'll need to fix the admin account access first. https://confluence.atlassian.com/display/DOC/Restoring+Passwords+To+Recover+Admin+User+Rights details how to get admin access back.
-
There are two errors here. The adaptavist one is likely to be due to incompatible versions (upgrade the plugin) The not permitted error is due to broken permissions. You'll need to look at the user's groups and settings and compare them with the general global permissions
-
Most of it depends on how you're trapping the exceptions, but the basic approach is simple - poke something into Jira via it's REST api
-
It doesn't really matter how many projects you've got, the point Svante makes is that the rank of an issue isn't a field you can just enter, it's a position in a list releative to all the other issues. It doesn't actually make any sense to try to rank an issue without the rest of the issues around it available for…
-
Yes, Cloud has a load of restricted functions, so "you don't have the admin rights to do it" applies. I really should have said that before.
-
If it's the icon I'm thinking of, those are configuration items you cannot change in that screen, either because you have set up something else to disallow it, or you don't have the admin rights to do it. The items are rendered because the setting is information an admin might need to see, and the icon is there to tell you…
-
That's actually a bit of a lie - a lot of them are still in date. What you mean is "Some of them are out of date and it seems to be the ones I've looked at"
-
Yes, that's much more clear, thank you. You've still not explained what a "requirement report" is though. There's nothing by that name in the core of Jira, or Greenhopper (hence my question 4 - it sounds like a plugin might be giving you more functions than we're familiar with)