Comments
-
I'm afraid not. Project admins get to edit components, versions and roles. That's it, no separation. Atlassian are looking at it I think, as part of a wider "make admin more granular" review. See https://jira.atlassian.com/browse/JRA-3156
-
Oh. Right. You can't do it in that version. You need to upgrade to Jira 5.2 to get a gadget that does column orders.
-
It sounds like the gadget you are using does not support the ordering of fields - what gadget is it and what version of Jira?
-
I'm not sure that it will work for Jira, but I've seen "setcap" used to access privileged ports with non-root users. You could try rinetd to redirect incoming port 80 to 8123 or whatever Your firewall could be persuaded to remap as well, but I'm not going to claim any knowledge of iptables I also have a feeling (don't…
-
The only thing I can think of now is to check your logs for errors. Beyond that, I'd reach for Atlassian support, as you've ruled out all the errors I've seen in this before.
-
Ok, this is a "shortening" search, not an "autofill". As you type, it should be shortening the list of projects beneath it. Could you pick an unusual word in your project names and type it in? Does the list below get shorter or not?
-
Next question - which "search" are you using? And what version of JIRA?
-
Ok, can you go directly to the project?
-
What does "not working" mean? You type in something and hit return and nothing happens? You search for a project and it finds nothing? You can't type in the field?
-
No, it still needs all those rights for Active objects and upgrades. (Although you could arguably lose the "drop and alter" during normal running when you don't upgrade the core or any plugins)
-
Depends on exactly how you want to do it - it's not simple code though. The most simple version would be something that automatically inserts new options into a select-list's list of options (which needs admin rights) and you'll need to decide how and when an insert happens. Of course, you could just create a new field and…
-
Not directly, you'll need a bit of code to populate the options on those fields
-
It could be - it depends on your processes and reporting really. The build number of a product can be veryeffectively used to populate the versions list in a project, the only real requirement is that you are working so that projects have a clear 1:1 relationship with products (you can have projects that don't have any…
-
Well, that narrows it down, but I really don't know what could be triggering it now.
-
Ah, authentication, it could be something to do with external authentications if you've got something outside JIRA that does it. There are a couple of authentication products that claim to be compatible with JIRA, but aren't actually, and just do "password safe" type things. If you're using one of them, and it's java…
-
It's the only part of JIRA that I know that runs on the client side. You won't get the error on the server side, other than a warning in the logs
-
It's probably around the screenshot functions - that needs java on the client machine rather than the JIRA server. It's a Java warning rather than a JIRA one, it's all about the client.
-
Why would you expect a macro that is provided by an addon to exist if you have not installed the addon? Bit like me asking why I can't make tonight's lasagne because there's no pasta sheets in the cupboard because I've not been shopping. Anyway, you need to install it. If it's not appearing in the marketplace listing then…
-
Please stop posting about other questions. That is not the way to get any help.
-
I tend to stay away from the javascript ones, it's probably my weakest area in Atlassian products, and there are better qualified and more expert people out there for you.
-
Ok, so you're telling me the field appears when you look at an issue? That's what we need to know. You shouldn't need to worry about it being on-screen much, all we need to know is if it is valid for the project and issue type. Try editing the issue and check you get the field offered to you?
-
You need to have "view workflow" permission in the permission scheme for the project you are in.
-
You need to look at the configuration of the workflow. It sounds like you have set up a workflow post-function that tries to set the "resolution in issue" field to something, but you have configured the field to be unavailable to the project. I am guessing though, it's just a hunch. To confirm this, could you check whether…
-
Er, it's not my documentation. It would be better to start with a working 2.10. As you have a backup of the database and attachments, you should start by getting that working. The problems you're having with the upgrade are suggesting that simply pointing 3.5 at the data is not going to work, and you need that XML out. The…
-
As I said already, you can't get the xml out of that. The reason I've suggested going back to your 2.10 and getting the xml out is that whatever you've been trying to do before is not working with SQL and restoration. I think you need to go back to the beginning. You have a 2.10 system running - please, take a full backup…
-
The last two errors are suggesting that the system has not upgraded the data. I'm afraid this setup is in quite a bit of a mess - I'd want to go back to the 2.10 installation and start again - export it to xml and try to import it into an empty 3.5
-
* That suggests that the licence you had in the 2.10 installation was invalid, as going back to it should be using the existing licence. So how were you running it before? 2. An xml backup has nothing to do with SQL. To generate the xml/zip file, you need to run the Confluence from which you want to take the data and use…
-
I don't have a note of the "recover admin password" doc for Confluence 2.x, but there should be one. The first step is the email you've already tried, so you'll need to start looking at the database next.
-
Restore the backup you took of the 2.10 data
-
Ok, sorry, been a bit distracted today. So, you have a 3.5 system that works fine. You now need to recreate the old database from the backup into a nice clean empty database using the standard database restoration tools for it. Edit the dbconfig.xml file in <confluence home> so that it points at the new database, and then…