Comments
-
Do you want your interns to have bulk edit or create shared objects? Sometimes it's fine, but if you separate it completely, you have full control
-
Start with the standard docs http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions http://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions There are no "step by step" instructions because we don't know what you've set up already. But the general principles: * Define global permission…
-
Atlassian's release notes strongly imply "no". Service Desk 1.2.7 is only flagged as working up to JIRA 6.3.15. Now, of course, there's no harm in trying it in a test system. So I did. It worked initially, but fell over when I converted an existing project to service desk, and with a new clean SD project, fell over on…
-
You are wrong about the upgrade path - you should be going from 3.2 to 3.5, then 5.0 and finally 5.5 Collation errors are likely to be down to your database having the wrong collation settings in the database, on top of the errors you have probably introduced by not using the correct path through the versions. For later…
-
Well, things have moved on, but... I'm still unconvinced by the search (sticking with google site: is a giveaway), although it's certainly faster. We're still getting at least weekly questions on restricting the issue list, using SQL and field security. Still no way to say "<sigh> see questions 5, 9, 12, 34, 56, 82.... (of…
-
This isn't about the documentation, it's about people asking the same question over and over and over. Not because the documentation is bad, but becasue they simply can't find a useful answer (of course, there's nothing we can do about the people who can't be bothered to search, but it's obvious a lot of people do search,…
-
Same here. I have much better luck with google using the site:answers.atlassian.com option.
-
Ah. You may well need to re-install the plugin, delete the field and then remove the plugin. This is because JIRA can't get a handle on fields that it can't find the code for. Because there's no code, it doesn't know what to do with the field for a lot of things, including delete.
-
This usually happens when you've installed a plugin that provides a custom field type, created a field of that type, then removed the plugin without deleting the field first. JIRA has a reference to a field, but can't find the code to support it because you've removed it. There's no easy fix. Start with "select * from…
-
Mmm. It'll shorten your searches, yes. But it might not be the ideal way to approach it. An old site of mine did it differently - they changed the indexing *write* with their "archive rule". The reason they did it that way was that just de-indexing means the issues crawled back into the index if anyone stumbled onto an…
-
Jobin's link is exactly what you need to work from, but it's a bit wordy. You should work through it to find the bits you need, but I don't think it makes it clear because it's (rightly) quite generalised. Thing is, your question is 95% of the way to answering itself - you already say you want to see a field when you look…
-
No, not closed, there just wasn't any response. Although Fred posted a good list of what was in use, there's no explanation of why versions don't work. The charts that require a version really do need you to do versions roughly as designed, and are essentially useless without versions. The ones that don't need versions,…
-
Most places that demand a version to be used do it for good reasons. Could you explain which reports and gadgets you are trying to use without them? So we can explain why it's needed and see if we can find alternatives.
-
Thanks Scott! Shame we can't vote up comments!
-
Same here. But Answers is "Confluence on PostGreSQL" as far as I can remember.
-
Let me guess, MySQL database on the back end? The recommended config for MySQL doesn't support the higher end unicode characters. It's caused us huge problems when people had used emojis in their data and we were trying to migrate on to MySQL. We could have stripped them, but the easier option at that time was to jump to…
-
Excellent! My next trick was to try the database connection manually and hence see what Jira sees, but you don't need that now...
-
No, the "first install" is decided when Jira looks at the database you've connected it to. If it finds something like a Jira installation, it will check it for upgrades, if it doesn't find anything, it will attempt to create empty tables and run the setup wizard. I'd guess that it's found an empty database, or even can't…
-
Ah, yes, "we don't know why". This is probably a killer - if you don't know why, and you can't find a source-controlled copy of the "edit-webapp" directory, you're acting blind, and you'll have to work on the assumption that they didn't make any hacks. So, on that assumption, yes, you should be able to install the same…
-
First, examine why you've used the WAR installation. It was either because you don't want to use the bundled Tomcat or you've got customised code. If it's the application server, then all you need to do is plan to support Tomcat instead of the old one, fire up the new installtion and point it at your current database. If…
-
Put it on a transition screen (*never* on create or edit screens), or set it in a post-function. Both those options have to be done in the workflow
-
My bet is on Dieter's "do not email myself on my own changes flag", but if that is set to mail you on your own changes, then the next step is to nip into Admin -> Mailservers and try a test email - that ignores the flag and will tell you if your email delivery chain is actually working. If it arrives, it's your…
-
Ok, I think you'll need to read your log to see what the error actually is.
-
Someone turned off the module providing the "table" macro? Check for spaces around the braces?
-
You'll probably find a reason in the log files. Before trying again, you should probably understand that so you can work around or fix it.
-
Remove them from the project-administrator permission. You need that permission to be able to add components.
-
No, because you can't do it in an add-on. The group and user handling is part of the core functions.
-
No Change. JIRA itself doesn't support them either - there's just a tweak in the directory stuff that flattens them out when they're used in external directories.
-
Are you 100% sure that your user is in the project role of Administrators? Bear in mind that this is not system admin rights or anything like that, it really is just "are they in the role, or in a group that is in that role", for that one project.
-
Step back for a second and check over the permissions - could you tell us: * Exactly what permission scheme your project is using * Exactly what the line for "modify reporter" says. It will be something like: role (developers), group (jira-developers), single user (Fred) * If the Reporter field is clickable on the issue…