Comments
-
I'd also check the "community licence" option as well, as a lot of charities are eligible for free licences. I don't know how it works in other countries, but in the UK, some of our museums are run as charities, and as long as they also meet the additional "secular" rule, they would qualify for the community licencing.
-
Look at the "attachments" section in your screen shot. It gives three rules - who can create attachments, who can delete their own attachments, and who can delete any attachment. Your account obviously matches the rule for "delete own", as that says "any logged in user", but the rule for any attachment is "people in a…
-
Administrator rights are irrelevant. Can you show us the permission scheme for that project, and explain how your account matches the delete rules?
-
This is not something you can think of in isolation from the rest of the migration. Are you copying the database, reusing the same one or using xml? Most migrations tell you to copy the whole home directory, not just the plugins directory, so you get the addons automatically, unless you're starting clean, in which case you…
-
Yes, but you'll need to do a spot of coding. See https://confluence.atlassian.com/display/JIRAKB/Customise+Word+Export+Template+for+JIRA
-
It might be, if that's how your Crowd has been set up. Does the database match?
-
I read that as saying you are looking for the crowd.properties in a database? It's a file in the installation, not data.
-
Best we can do is * Stop Confluence * Modify the values specified in the cwd_directory_attribute table within the Confluence database manually. The values must match all the values specified in Confluence's crowd.properties * Start Confluence We can't tell you how to modify your database, as we don't know what it is.…
-
The editor in JIRA is a plain text editor, not a rich text one. It stores and edits plain text, and it can then be told to "read this text as wiki markup" which makes it display the text with formatting. Atlassian have requests outstanding to bring the Confluence edit style into JIRA, but I'm not sure how far away that is.…
-
Well, two answers... In plain Jira, you'd add custom fields to handle these. Standard well documented functions - see https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field You'll benefit from a read of that, even if you look at the other thing on my list: Have you looked at "Jira Service Desk"?
-
Argh. You really should have told us that before. You DO have the "plugin" links referred to in your original question, and everything is working barring the marketplace connection. You have two options 1. Fix the link to the marketplace. It's probably a firewall on your server or network blocking outgoing access to the…
-
Those links ARE the universal plugin manager. When you click on "plugins", it takes you into the main body of it, which is titled "manage my plugins". It will show you the currently installed plugins and has a search for new ones. Just type greenhopper in there and you'll find it and be able to install it. Have a look at…
-
Ok, so if you click Administration at the top right, you should go to the main admin pages - look for "plugins" on there (near the top of the main body of the page). Or look for "plugins" on the menu bar that you get when you're in admin mode
-
Can you confirm what version of Jira you are running? (It's in the footer at the bottom of most screens) I ask because your comment about "system section in the left menu" implies you are on version 4.something (or 3!) and not version 5. The UPM only became available in later versions of 4, so if you're on too early a…
-
The detailed answer for your actual question is irrelevant, because, well, see https://confluence.atlassian.com/display/Support/Support+Response+SLA's
-
You're right, you need Agile (or Software if you're on JIRA 7+) to provide the ranking field. The only way I can think of doing this without ranking is to * Prefix the names of the issue types with numbers so you can sort on them (feels clunky) * Find/write a scripted field that can do it for you (advantage - you can embed…
-
Much as Andy said before, Jira plugins are pieces of software that you deploy in Jira to provide additional features.
-
The general advice here is "don't delete users". If you delete users, you are deleting potentially useful historical information. Jira stops you from doing it precisely because it's trying to preserve your audit information. When someone leaves, remove them from all their groups and roles and then forget them. It takes a…
-
Yes. That's a very short answer, but there's not a lot more to say. You can use it to handle all sorts of processes.
-
Excellent. From there, you'll want to look at the permission scheme (issue security schemes will hide issues, potentially all of them in the project, but not the whole project)
-
That means you can get to the project via admin Although you might not have any right to see it at all, that's a user setting. Admins can always get to the admin screens in projects, even if they can't normally see the project. Go to Admin -> Projects -> List of projects. (Not just "projects" on the top bar - that's the…
-
From what I can remember of the last time I used it, the plugin does not store the information that email was sent. It really does just send it and move on.
-
Yes, just pit the field on the issue view screen and nowhere else.
-
Not sure if you mean the certificate for running it over SSL or for it accessing SSL protected services. See https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-over-ssl-or-https-802593051.html or https://confluence.atlassian.com/jira/connecting-to-ssl-services-117455.html depending on which it is.
-
Ok, but does your account have the rights to see things in that security level?
-
You don't need to. Search the project for everything and the users in groupA will see their 50, and not the ones for groupB because they're hidden. There's no need to involved the security level at all. If you have complex security schemes or you're using it as data as well as to just hide issues, then you can search by…
-
The point of a security scheme is that it hides issues that the user can not see. You can't search for something you can't see. So, I'm afraid Jira is doing exactly the right thing here - not leaking information you've chosen to hide. Or have I misunderstood the problem?
-
No. It can't be - the problem this addresses exists because there is nowhere to store the creator at the moment. It's not logged, it's gone, was never written anywhere. The entire nature of the problem was "person entering the issue is not recorded in any way". So there's no way this can be retroactive. In fact, if it…
-
Probably because you don't have permission to view them. Admin gives you admin rights (including the ability to change permissions). It does not mean "can see everything", as that's a very poor permissions model. If you want to see a page, you must meet the rules the space and page have set on them (those rules could, of…
-
Both can be done with simple Jelly escalation scripts - see https://confluence.atlassian.com/display/JIRA/Jelly+Escalation