Comments
-
That is the safest easiest route, yes.
-
No problem - it's always worth asking!The question for me is if you're trying to upgrade or just import some bits from 4.3.2? I've covered the upgrade side of it, but if you really are just wanting to grab a couple of spaces from an old system and import it into a 5.5 and it's just the raw data you want, then that's also…
-
Start by stopping thinking of this as a "restore". It's an upgrade - you're upgrading from 4.3.2 to 5.5.4. See https://confluence.atlassian.com/display/DOC/Upgrading+Confluence As for "making it look and feel like 4.3.2", that's a non-starter. The upgrade will include all your settings and internal configuration, but the…
-
Start at https://confluence.atlassian.com/display/CROWD/Overview+of+SSO
-
Ahh, bother, you can only do the "create subtask/copy/clone" script with SR for Cloud, I think.
-
I'd use a web-fragment in the script runner add-on with a "copy issue" script behind it...
-
That's what the schemes are for. How else would you do it? (Well, without rewriting the whole screen and scheme setup)
-
That is exactly what the field configuration schemes are for (mandatory has nothing to do with screens - all screens do is list fields to be presented) You need to divide your field configuration schemes into two - one for each group of projects.
-
You can't do it directly, Jira doesn't do field security (and OnDemand doesn't let you install plugins that do it) What you can do - remove the field from the edit screen (and possibly "create"?). Create a screen that does include it (actually, you can re-use the "view" screen, but often that doesn't fit with this trick).…
-
Yes, you can customise your installed version - download the source code, amend it, recompile it and install it on your server. See https://confluence.atlassian.com/display/JIRA/Building+JIRA+from+Source Having said that, you might not need to redo the whole thing. Depends on what you're changing - if it's just .jsp files…
-
You don't, mostly. Only issues and versions really fire events, although the list is growing. For writing them, see https://developer.atlassian.com/display/JIRADEV/Writing+JIRA+Event+Listeners+with+the+atlassian-event+Library And, no, you can't install add-ons into OnDemand.
-
Could you re-read what Bart and I have written please? >Would it be possible to get list of all projects, with each project, its enabled roles, granted users & groups in each of these roles. This will enable us to understand who all have access to which projects. You can dig out that list, yes, but it won't "enable us to…
-
What Bart is getting at is that the list of people in roles or groups tells you virtually nothing on its own, and can only answer "who is a member of this project" in one very simple use case. For example: * In project 1, I can create, edit and comment on issues * In project 2, I can comment on issues * In project 3, I can…
-
You need to save the filter, then click on "columns" near the top right.
-
When it's ready. I think we're going to see quite a few iterations of JIRA 7 before 8 hoves into view though.
-
Costs of JIRA are based purely on the number of users, not projects. So in terms of licence costs, it's irrelevant. In terms of admin costs - archived projects won't make work for your admins.
-
Depends on what you mean by "hosted". Cloud is a "hosted" offering, there are other 3rd parties that do hosting (you'd need to ask them about what they support), and you always have the option of running it yourself (that's "Server" - not "hosted")Which one do you mean here?
-
Not really, the only thing you can use is Google applications - see https://confluence.atlassian.com/display/Cloud/Managing+Users+and+Groups+with+Google+Apps
-
Oooh, that looks like it will solve this problem, thanks Daniel! It might be able to help us with the fundamentally broken searching in Confluence too.
-
Because you are not in the space administrators permission. System admin is there to let you administrate the system, not spaces. As such, you can adminstrate the permissions and add yourself, but it doesn't grant you any automatic rights over a space.
-
I'm afraid not. On server versions, there's a minor tweak you can make to the template that makes the field single-select. On cloud, you don't have access to the templates. You could stop using components and swap to a single-select, but you will lose component lead functionality, the ability for the project admins to…
-
Have a look in the documentation for "creating or commenting via email"
-
You should use the latest versions of git, and check your log file for more errors.
-
You need to read the log files to find out why the application is not starting correctly.
-
What gadget, what makes you think you should see it, and where?
-
No. Because the field contains the data. That's a bit like asking "can I remove the bottle from this bottle of water and keep all the water?" Where does the water go? You no longer have a container for it.If you want to keep it, you have to put it somewhere else. Use bulk-edit to place a copy of the data in the other field…
-
I'd strongly recommend that you don't do this. Removing a field from a field config scheme requires hacking core code, which is unsupported, an upgrade nightmare and a lot of work for no real gain.
-
Er, I already said you can't.
-
The whole point of a field configuration is to allow you to show/hide all the possible fields. So no, you actually need them all there. Even if you've used field context to remove fields from projects, you still need them in the field configurations, in case you decide to re-include them.
-
You can't - the types available are controlled at a project level.