Comments
-
Yes. For Confluence, use the "anonymous" permission in each space For JIRA, allow the "group" called "anyone" to have "browse" permission in the permission schemes. In both cases, do NOT allow these roles/groups any other access without very careful thought, as they can allow unlogged untraceable changes to be made.
-
Not without amending core code. The crossing out is (as you found in the docs), completely based on Resolution. This does make some sense given the structure of Jira actually - I've got quite a few workflows that don't have "closed" at all, and there's a long conversation to be had about it. Driving it off Resolution is…
-
The operating system may have used a bit too much /tmp or other working space while supporting the JVM, and Confluence (well, the Tomcat running Confluence) will chew up space on the installation directory too (typically under /opt if it's a default installation There's no way of knowing what filled up your disk without a…
-
You can try the same javascript as the length, but use "width=" instead. You may want to experiment with measurements (e.g. width=50% or width=400px. Remember to check it on small and large screens)
-
That's correct. Although the mandatory thing is incidental. The point of bulk change is that you make the same change to all the issues you have selected. If you change a field, then the new value is supposed to go on to all the issues selected. The mandatory flag is just making it a bit difficult for you - it's not…
-
I'm guessing that a "defect" is a sub-task on a story? I'm afraid you can't move sub-tasks like that. Because they are explicitly part of a story, they move with the story. You need to move the story, or promote the defect to an issue level and move that (which tacitly states that the defect is no longer part of the story)
-
Atlassian's policy is "when it's ready". You'll know the release date when yhey release it, and not before. You can take good guesses based on the state of OnDemand, blogs, mailing lists, and so on, but you won't get a concrete date unless it's really imminent (the furthest ahead I've known is a friendly informal email…
-
Atlassian's policy is "when it's ready". You'll know the release date when yhey release it, and not before. You can take good guesses based on the state of OnDemand, blogs, mailing lists, and so on, but you won't get a concrete date unless it's really imminent (the furthest ahead I've known is a friendly informal email…
-
What makes you think it might have one, or even need it?
-
The ones mentioned in the answer linked to above.
-
I'd agree that the flaw might not be a bug, per se, but "not bothering to tell the user why I'm losing them time and data" is.
-
The latest versions of Office seem to have bugs - see https://answers.atlassian.com/questions/39432356
-
Remember that you'll also need to provide them with a group to allow them to log in, and remove them from all groups that give them permissions on other projects (i.e. work out how to remove "jira users" from all your other schemes)
-
You either need to allow the client some form of access to your system, or export the documentation for them.
-
Correct. All the stuff that is handled by "schemes" is a Jira Admin job - permissions, notifications, issue types, screens, fields, and so-on - all Jira admin stuff.I did forget one though - if a Jira admin selects "simplified workflow" for a project, then the project admins may also add/remove status from the workflow (An…
-
Project admins can maintain the list of versions, components and users in roles in their projects. With JIRA Agile, they also get the ability to start and end sprints, and maintain boards. That's all they get over a "normal" user.
-
Some of it is possible with the plugin, I think, and SQL can answer more. But there's a couple of quick points: 1) You need to define "top users". Is that contributors? (People who add/edit) or just everyone who wanders around? 2) A lot of this stuff simply isn't logged at all, and you'll need to look at your web access…
-
It depends on exactly what you want to restore if something goes bang, but there's three simple things to get a backup of: * The database - you need to be able to recreate an identical copy of the database for it. * The installation directory - possibly optional, as below * The "home" directory - possibly not all of it, as…
-
Tomcat is the application server within which JIRA runs. So yes, Vijay is probably right, as a default installation will place the atlassian-jira directory immediately beneath the root of the Tomcat installation
-
Could you try putting it in the place that worked for me instead?
-
Last time I did this, <tomcat>/lib worked. For PostGreSQL. Make sure you get the ownership and permissions on the file correct too (look at the files already in there, set it to the same)
-
The first error occurs because the database driver is not installed anywhere that the Tomcat running your JIRA can find it. The second error is occurring because this.class.classLoader.rootLoader.addURL is not a valid method - by the time you get to the rootLoader part of it, you have a null. The null may be further up,…
-
Sounds like someone has put the Resolution field on the Edit screen - check that first, and if they have, remove it immediately.
-
Not natively, but check the marketplace for "pro fields"
-
I'm afraid this is an incoherent question - evaluations, upgrades and reports are all mentioned and there's absolutely nothing to tell us what you're actually trying to do, or what you really want. Could you explain please?
-
Not without code, that's pretty much a hard coded layout.
-
It sounds like you have an option of "none" on the list of options - that's why the "mandatory" flag is picking it up as being filled. If you reconfigure the custom field, you should be able to remove the default, and then disable the "none" option. JIRA will then present the user with "none", still, but it will mean…
-
Right, those look like Tomcat and Confluence are unable to read/write the file system in the rigtht places.Check the ownership and rights on ALL the directories you've set Conflluence to use.
-
Yeah, you're definitely missing a lot of the function - the css has vanished, as has the templates.I'm afraid you really do need to consult the log, we really can't tell you anything without a look at that. It should be rammed with errors as Confluence starts up.
-
What does the log say is going wrong?