Comments
-
The right to create boards is controlled only by the "create shared objects" right in global permissions. If you don't have the option to create a board in "manage boards" at all, then you don't have that permission. Importing from CSV, load balancers and apache have nothing to do with creating boards. I would check…
-
As a partial answer, you're looking in the wrong place. Sprints do not belong to projects, so there is no direct relationship between them. Sprints belong to boards, and can cover many projects
-
The instructions are at https://marketplace.atlassian.com/plugins/com.intenso.jira.plugins.suiTest/server/installation
-
Use the latest one.
-
Yup, a label is a global thing, it doesn't really care about the project. There's no way to "clear them out" - Jira is suggesting them based on previously entered data in other projects. Basically your gut instincts are spot on!
-
Good point there as well - I didn't really notice the extra label, and I can't see why it's there either!
-
There are not really any questions here - you appear to be listing some of the things JIRA can do rather than asking us about them. What do you want to know about these functions?
-
It depends on how you use the internal database. If you are using "export to xml, then import", and not using the system during the changes beyond a little bit of testing, the hsql stuff will generally work. But I would much prefer to use postgres throughout. Obviously, stick with the supported versions for whichever JIRA…
-
No, jumping to 6.x is very unlikely to work. Step through versions. Test before each jump. Jira will NOT handle anything if you try to jump too far across versions. Plugins depend on what they are. If there are dependencies, then you need to look at each one in detail and work out what the upgrade is going to do to it.…
-
Test the whole process on a copy of production. Take backups Step through versions - 3 to 6 is probably not going to work and you'll need to plan and test it. Assumung you're on 3.13, I'd consider 3.13 -> 4.0 -> 4.4 -> 5.1 -> 6.1. But your testing should uncover any issues with that approach. Analyse the plugins in use for…
-
Right, this is simple. Subtasks are irrelevant in planning a backlog, so they are not displayed there.
-
Ok. There's a couple of things here * Admin means "administrate system", not "can do anything". Unless you've added admin groups to a security scheme, it has nothing to do with issue visibility * Guess #1 - although the subtasks say "not visible", you can actually go to the full view of their parent issue and see them…
-
Couple of quick questions - From where are you creating the subtasks? Do you have any issue security in place in that project?
-
You'll need code to hide the bar, although a read-only user won't get the "create" button as they can't do it.
-
Field configurations are flat. If a field is mandatory for an issue, it is mandatory. So you can't do it. What you could do is have different workflows for each issue type, and place "field is mandatory on transition" validators on them. This would not stop someone moving an Incident to a Defect, but they would not be able…
-
Last time I used Rally, all it could export was CSV of the plain data (no real history etc) or a block of XML. The CSV can easily be imported into Jira, but I'm not sure what is in the XML - if it's got more data like the history and attachments, then you could use that to generate something to import into Jira.
-
I'd suggest you raise that with Atlassian support - when plugins misbehave, the first place to check is the logs, which you can't do directly.
-
You don't get those rights for OnDemand. See https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy
-
Put the estimate in the original estimate field, and the use the "log work" function to log time against it.
-
My guess is that the read-only access is being caught as a change to the data, so it's asking for a rebuild.
-
Does your backup process touch the files in the home directory in any way? And are you backing up the database with the database tools?
-
Not a clue. You need to explain what all your words mean - navsea, nmci, japan on onenet, etc
-
It's no different from merging into a separate set of installations. Agile-ready is just the same applications bundled together - it simply saves you some of the integration work you'd have to do if you installed them all separately (that makes it sound like the integrations are a quick piece of work - they are relatively…
-
Hmm. The Jira I tried it with is pretty much empty. One project, 6 issues, two custom fields and using the default workflow. Maybe it's the Agile or Service Desk plugins doing this...
-
Actually, yes, it does. I just tried it in 6.1. If the user leaves either version field or the components unfilled, it inherits the values from the parent
-
Check your project permission schemes. It sound like you haven't granted your user "browse" anywhere.
-
I don't think we can help you until you tell us the answers to the questions I just asked - where is your javascript? ("default javascript" is meaningless in terms of Jira and does tell us where it is). What does it say, and how have you implemented it?
-
There is no such thing as "default javascript". You've wedged something in somewhere and to help you debug it, we need to know where you've added it, what it's trying to do and probably see the actual script as well as the stuff you've surrounded it with.
-
You'll need to contact the vendor to find out when (if) they are going to release a new version
-
Ok, cross off option 4 then.