Comments
-
Not quite. The fixes and patches for 6.6 will go into 6.9.2 and above.
-
So "module" is a custom field? And Selected means "the current value in the field"? You still need to explain what "get" means here.
-
There's no way a computer can tell if content is "valid". It sounds like what you really need is a workflow for having people write stuff, and the admins "authorise" a releasable version. Is that right?
-
But they can't work because you don't know what the "current project" or "current board" are unless you're inside them. Yet again, please tell me what the "current project" is when I am looking at a filter for "project in (x, y, z)"
-
There's a field called "Analytics PPL List" if your question title is a copy and paste of the error message. If there's no field by that name on screen, then your admins have removed it from the screen. Check if it's there when you edit an issue though.
-
Please explain * what you mean by "get" * "contents of the module" * what a "module" is * where the "selection" is done
-
You've found the "enterprise" release. 6.6 is the version that will have long-term support, with important bugs and patches going back into it. It will not gain new features like the later versions will, but it will be supported for a long time, unlike the others.
-
Your admins have put a validator in the workflow, or made the field mandatory in the field configuration, to force you to enter this field as you create the issues. You'll need to fill in the field, or talk to your admins to get the mandatory flag removed
-
I've got a 7.8 here that has an export button - word, xml and printable. You appear to be missing the export button completely, which suggests one of your admins has removed it somehow.
-
They descend in number because the later versions are more useful and more downloaded than earlier ones, so you want them at the top of the list. There are gaps in the numbers where Atlassian pulls releases (incompatible libraries used, security flaws or license issue have been reasons in the past)
-
Jira only does Epic > User stories > Sub-Tasks so use that.
-
That error message usually suggests that the garbage collector was unable to find any new eden space in the memory to use and hence fell over and stopped everything. You'll need to look at the memory settings for your Jira - what are the -Xm<things> settings in the setenv file (.sh or .bat depending on your server OS)
-
7.anything to 7.11 can be done in one step.
-
Ah, hang on, you've got a .war installation. These are not supported any more, and can't be upgraded by the installers. You'll need to convert to a standalone 6.1.6 first, then you'll be able to upgrade it.
-
You're going to need to explain properly if you want us to help you with something.
-
From the error message, I'd guess you have a field called "Reason for the bug" that has been made mandatory. Any admin could have added the validator to the workflow.
-
Looks like you removed the "children display" macro from the page. (I can't be sure it's that macro though, as you've obscured too much and I don't know the structure of your confluence)
-
The Jira you are trying to update has a validator that requires the entry of a field. Your code is not filling the field in, so it fails validation. Either remove the validator, or send data to go in the field
-
Exporting large numbers of issues is creating a problem (when you go higher, the export affects the performance of the system), and in fact usually indicates a broken process as well. You should be looking at why you think you want large exports and fix that.
-
It will be issue.getProjectObject().get<project thing>()
-
I'd guess you are not a full administrator. Check your groups and the global permissions.
-
Jira does not do assign to groups (because it is a terrible practice that never works in real life). You can use a custom field to capture a responsible group though, no harm in that, and keep the assignee for the actual person who is currently responsible. But JSD already has something for this - the intention is that any…
-
epicLink.status gives you a status, not a string. Try def st = epicLink.getStatus().getName() instead
-
As it's working ok for most countries, we have to say it is something to do with the routing or firewalls between you and the BB servers. That's not an Atlassian problem, it's something for your network providers.
-
That is a very provocative, and potentially loaded, question. And an excellent one. I am an Atlassian fan-boy, and hence biased towards them, but "what problem did you solve?" is an impossible question for them. Because the answer is "nothing". The old UI was not great, but the new one is almost unusable.
-
Or pop a transition screen to ask the user for a resolution.
-
Your "integration" is not working correctly, it's not picking up new issues in Jira. You'll need to look at the "integration" to see what it is doing and configure it to look for the changes.
-
It's still what Mirek said - set the resolution in the workflow, either with a screen or post-function.
-
Nope, they don't. There's a link derived from "this board includes a project", but that is not the same as "board belongs to project". And, as I've said before, a board can include issues from many projects, and projects can be shown on many boards. So "project = currentBoard" could return many boards, and is useless on a…
-
>I specified the correct path, which is /opt/jira.home Nope, that's the wrong path. You need to give it the path to the installation, not the home directory (sometimes called the data directory). Have another look at the system information page, that will give you the installation directory (near the data about the home…