Comments
-
Should be remote, if I remember correctly
-
There are no "dependencies" - each Atlassian product works on its own (given the right hardware etc), although Crucible runs as part of Fisheye, so you get Fisheye with it. But there are some very good interactions between them. We often find running Bamboo alongside Fisheye, Crucible, Bitbucket, and JIRA works very well…
-
JIRA has complexity like this because it's immensely flexible. While the defaults are something you can "pick up and use", you do need to put a little effort into understanding it if you want to get the benefits of its flexibility. In this case, Story Points are something that only belong to standard Scrum issue types, and…
-
No, because the systems need the user to be able to see the data the charts are being generated from. You need a third party to interfere - one that can read JIRA, generate reports and publish them for someone to see (hence leaking information) without access to the original data. That has uses, but it's not supported by…
-
Yup, I do that at least once a day! Validators are a bit limited in Jira when you first look at them, but there's a good reason - the combinational logic you're talking about is the sort of thing you can't code a generic approach to. Every installation, every requirement, every transition could need something different, so…
-
The field must contain a text based field. Not dates, numbers or options (select lists and their variants), it's got to be text based. There's no point in reg-exing non-text fields, their values are controlled and validated already, a user can't get them worng.
-
Oops, I meant "upgrade to a version released after the end of your licence"
-
Support and the ability to upgrade. (And your dev licences end too)
-
I usually use tabs on screens to break up large lists of custom fields. Would that work for you?
-
The 5 digit number you've found is the ID of the option in the customfieldoption table. You were almost there
-
It looks like you are compiling some code in an environment that does not have any of the dependencies or libraries you need imported correctly. How are you compiling this code? Are you using the Atlassian plugin SDK at all?
-
This is a classic symptom of "database tables out of line". JIRA stores the status and the position in the workflow separately, and does this if they get out of line - it's like it doesn't know what transitions to show. Try the integrity checker, selecting the workflow options. That should identify the issues affected and…
-
Not natively - a component is a project object, so it's available for all issues in a project. You'd need to code to make it user related.
-
http://www.plugenta.com/jiraauditor/ does all of that, and a lot more. Very neat, and useful plugin.
-
Hard to tell - I've clicked on a couple of the download options and it's worked fine. Exactly which download are you trying? And have you tried it again in case it's a transient fault?
-
Hmm. At a guess, I'd say you'd installed JIRA with index permissions, and then locked it down later. Or, you might have run into the rather interesting case that JIRA core code would like to index the database, but can work without it, whereas Agile really needs it and fails if it can't do it. (Guessing at this one, of…
-
The application log file should have a lot more information on what is going wrong.
-
Projects don't have start and end date fields. You'll need to define what you mean by start and end before anyone can give you a useful answer.
-
A filter gives you a list of issues, which may be from one or many projects. I don't know what reporting you are looking at when you say "show its progress on the board" though, so I can't really tell you more.
-
Ok, so what error are you getting during the restore? Are you using the very latest server version of JIRA?
-
It will persist - you're taking JIRA Cloud data and putting it into a JIRA of a lower version than Cloud. It is just warning you that there may be incompatibilities if your data takes advantage of new features that have been added to Cloud that are not in your target version of JIRA. It is not an error really, it's red…
-
The portal depends on the project being a service desk project - that's the point of the project type!
-
No. Only IE 8 and 9. It might work ok, but it's not supported, so if you have problems, the response is going to be "upgrade"
-
I don't actually know. I have a strong suspicion that you have the script runner plugin installed, because on a standard Jira, you can't just whack in odd lines of code like that. See https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner Check that, and if it is what you're using, then the docs…
-
A validator can be thought of as a simple logical question. If the answer is yes, it passes, if the answer is no, it fails. Your logic says "if the user is a member of the group SWTL and resolution is not fixed". If you think about that carefully, what you're saying is that the person MUST be a member of the group SWTL and…
-
What are the connection errors and when do they happen? How are you starting Confluence? Which version have you got installed? Is PostGreSQL server running on the same box? Are you checking that comes up first if you've got all the services starting on boot?
-
p.s. it's not obvious, I missed it for ages
-
Look at the bottom of the "create project" popup box - there should be a line there that you can click to say "use shared schemes". It'll then ask you which ones to re-use.
-
Jelly went away in JIRA 6.4, that's why the link is broken. Standard replacements are to give the Script Runner add-on a go, as it has an almost drop-in replacement. Or Atlassian's Automation addon.
-
The usual way to do that is a variation on https://confluence.atlassian.com/display/JIRA/Jelly+Escalation