Comments
-
Either the project simply is not there, or you do not have "create" permission in it.
-
So the problem is simply that the user directory is showing your account 6 times. Everything else is fine? Very much sounds like a bug in the user directory display. I've not seen it before, except when duplicating accounts in Crowd by accident (although that was for everyone, not just admins) I think I'd raise this with…
-
But are all six showing with identical logins? What directories are they coming from?
-
Ah, yes, that clears it up perfectly, thank you. There appears to be six identical accounts - same email, same avatar, same display name. A few things I'd start looking at, mostly by descending into the actual accounts and checking all the details Look at the account IDs - are they all the same as well? (For example, on…
-
I don't quite understand what you mean here? You have 6 users and you've made all of them administrators? Or you have 6 users and you did not want them in the admin group and you don't know how they got in there?
-
The wizard is triggered by having an empty installation. You don't need to overwrite the damaged one, just create an empty one in a new place. Then the config wizard will kick off when you first run the new installation.
-
Well, not exactly, but I know what you mean!
-
Ah, no, that's not going to work. If you run the installation wizard, you get an empty Jira. That's it. It won't pull in bits of an old one, and the whole reason you're getting the errors is that you are not starting with a clean installation. You need to give it an empty directory, let it install an empty Jira and then go…
-
You definitely can't do this in plain JIRA. I'm not even sure you can do this perfectly with a script or plugin, although I'd try the behaviours tricks in the Script Runner plugin - that might be able to do it.
-
On a board, go to configure -> colours and choose to base the card colours on queries, then you'll need a query for each status/colour. I don't think that flows into the gadget too well though.
-
Yes, they are default off-the-shelf plugins, which you can perfectly safely disable and ignore them. I'm trying to imagine why you're determined to remove them quite so completley - in an active state, they'll use a tiny bit of Permgen memory, but if disabled, all they do is take up a tiny fraction of a penny's worth of…
-
No. Assigning an issue is an action outside the workflow. Although you could move some of it into the workflow and get some flexibility there, you'd still have the "assign issue" options available in the general actions If you were not using OnDemand, you could use the "auto-transition listener" - that can catch "assign"…
-
It is possible to add "remove file X" to the build scripts. Question is - why? The bundled plugins fall into two groups - ones that you need and ones you can easily turn off in the UI. I can't think of a reason why you'd want to go to the effort of doing this when it's easier to simply turn them off after installation.
-
I can't tell you what the address is, because I don't know what you (or your organisation) chose when you set it up. It will be http://<what you chose>.atlassian.net for a starter. For credentials, you'll need to talk to your admins/owners, and for "network settings", it's on the internet on a standard url, so I don't know…
-
Cloud is already "set up", that's the point of it - you buy it and it's run for you. What settings are you looking for?
-
I don't think you can. I think you can write something that will block or hide data from admins (although I suspect you might find it quite difficult). But, as an admin, I can disable or remove plugins... I think you'll need to tweak the core code to stop admins from being able to see it and remove it, and of course, you…
-
No, Jira doesn't do any of these things. Specifically answering your two questions: You CAN set a security scheme which doesn't include system administrators, that's quite simple - just leave them out. However, as system administrators, by definition, they have access to the security scheme and the rights to change it,…
-
That is only one possibility. We need to know more about the setup.
-
What version of Java and Jira are you using?
-
If you were not using OnDemand, I'd point at a list of possible options: Jelly (I don't think you can run this in OnDemand?) The script runner (No, you can't install this in OnDemand) CSV import (list of issues with the new values for the field and "add custom field on import" - don't know if that's possible in OnDemand)…
-
I've done this a few times with simple HTML forms that present simple information, gather minimal information from the users and then post it over into JIRA via SOAP. Nowadays, of course, I'd use REST instead.
-
No, you can use neither, either or both on a project and it's a project choice on how they use it. You can even take it down to issue level (e.g. hours on tasks and stories, story points on bugs). However, your boards can only use one or the other, so you may find it a little odd trying to do both on the same team.
-
Yes, you've found exactly the right place! Although you might want a quick look at the post-functions it does too!
-
Oh, yes. As a good Adaptavist, I always use Script Runner for this nowadays - it has an "auto transition" function that lets you choose some conditions under which you want to execute a second immediate transition and then does it. I think there are other add-ons with similar functions. (Before Script Runner made it…
-
Nope, sorry. If you can create an issue in the project, you have the rights to create one of any type in there. There are some tricks you can play on Cloud, but they're ugly - essentially they'd let the user start creating the issue, they enter all the data and then get told they can't create it and they lose all the data.
-
No. An issue type always follows one workflow, and all transitions have a fixed end point. So you can only have one "create" landing point. If you could get your dev team to raise one type of issue, and non-dev another, then you could di it by having different workflows for the different issue types. If you were on Server,…
-
Yes and no. There are three different things here. First, a "read only" user can be set up, and take up a licence, but it's not really needed if you don't need to think about security. If you add the group "anyone" to the "browse" permission in your permission scheme(s), then people can see your issues without needing an…
-
The permission to view a page is separate from edit, and from modifying files, that's all done by space permissions. However, this applies to the whole space - you get access to ALL of the files in the space, or none of them, it's not selective.
-
No, it's not synchronous like that. When a user opens a file for edit, the effective process is "download file, edit, upload new version". A user could easily walk off after download, and never "close" the file by uploading or explicitly abandoning it, so Confluence can't "lock" it - it doesn't really know if the user…
-
You really do need to read the logs - they will have connection errors in them. ODBC is not JDBC - you may well have the right settings for ODBC, but that doesn't matter - you need to get the right settings for JDBC and test with those.