Comments
-
Status is not a "field", it's an indicator of position in the workflow. You have to use transitions to change the status. For REST, see the REST Endpoint documentation
-
If I have understood this correctly, you have a project (or set of projects) that don't want to use components and/or versions? That's not a problem - leave the screens alone, and move on to field configurations - copy the current one to one called something like "hidden versions" and hide versions in that, then apply it…
-
No. That sounds like a problem in your installation, but could you check what happens when you re-run the filter (as opposed to just using "return")?
-
Ah, sorry, I don't tend to follow links because it's a bit of a faff and often a waste of time and effort (opening new windows, reading often scrunched up text, when all we actually need is the plain text of the error message). Ignoring the links made your post look like it wasn't really a Confluence issue. Anyway, Jing…
-
That looks like a Google drive problem, not Confluence. Could you explain?
-
You can't. You might try raising an issue with on demand support, but I don't think they support this and they will probably say no.
-
That looks like a source code download, not an installation. If you want that to run, you'll need to compile it and embed it in a Tomcat. I'd suggest you download an installation version instead though.
-
I could read that in two ways: * You want to automatically remove data from the issue when you resolve the issue * You want the user to see the screen you have posted, but with two fewer fields If it is the first, then your best bet is to add "post functions" to the "resolve issue" transition that say "clear field X" If it…
-
Right. You need to move those issues to the far right hand column, then you'll be able to end the sprint. Either change the workflow so that the tasks go to "done" rather than "task done", or change the column definition so that it includes done and task done.
-
That is not what I asked. Are they in the far right hand column of the board?
-
On the board, are these tasks all in the "done" column, on the far right hand side of the board? All in the very last column?
-
Yup, that answers it - there's some css in the standard global theme that IE7 doesn't handle properly. The documentation theme doesn't need it.
-
Mmm, the correct fix is "use a proper browser". The slightly less correct fix is "move to IE8 or 9". You should be considering that as IE7 is already down to a pretty minimal support model - you'll get little more than the odd security fix for it and bugs like this one simply won't be fixed. Anyway, to help identify where…
-
Try https://atlassian.com/jira
-
Not natively - the Service Desk application is aimed at being, well, a Service Desk. Inventory is a different type of function. A lot of people have used JIRA to do inventory management though, and it can work quite well with a bit of clever configuration (the usual approach is to have an inventory project with issues…
-
Sort of - the roles are a way to put users (and/or groups) into individual projects. But yes, you've summed it up well there. Yes, the downside of roles is that you need to add new users manually. But; 1) You can delegate that to the project admins. I.e. "your new developer in your team - up to you what projects you add…
-
Ok, I run into groups and roles all the time. Groups are simple, they do what you expect. A group is a set of users. The advantage to using groups in permission schemes is that it's blindingly obvious. If you say "Group ABC can do action X" then everyone in group ABC can do X in the projects you give that permission scheme…
-
Start at https://www.atlassian.com/software/views/open-source-license-request Note that on Cloud, you will not get to use your domain, it will be <something>.atlassian.net (probably javajackass.atlassian.net, but you can talk to them about the details later when you've decided whether to go for Cloud or Server) (Edit -…
-
You'll need to put an "if" statement into the javascript to detect the current space and only activate if it matches the spaces you need it for. For what it's worth though, opening in a new window/tab every time is a royal pain in the neck for most users as you quickly litter their workspaces with pages they don't care…
-
Yes, if you use Apache in front of JIRA, it makes things easier, and it's a recommended setup as well. Ideally, you run JIRA on 8080 without SSL, and firewall it off from the network. Then you run Apache, with SSL enabled, and a reverse proxy to the local JIRA. Apache does all the encryption work and Tomcat can get on with…
-
* Not required, but always recommended. * Yes, see https://confluence.atlassian.com/jira/running-jira-over-ssl-or-https-124008.html * Yes, you can change the port JIRA runs on to 443 in the server.xml for Tomcat - strictly that doesn't mean you don't need the port, but systems will assume port 443 when you…
-
What limitation? You've got a valid list of versions, it's available for reporting issues in "affects version" and when you plan to fix it in "fix versions", which then becomes "was fixed in" when you mark it resolved and eventually release it.If you've shipped a release, then mark it as "released". You will still be able…
-
Your process is basically broken as far as Jira is concerned - you're using fix versions in an inappropriate way and really should split it out into a "desired fix version" and "fix version".But no, you can't get different lists, because that's not useful for most scenarios.
-
That's wrong.First of all, how does an end user know when it's going to be fixed? It's not up to them, it's up to the development and/or product teams to decide when a version is due to be fixed. IF it's up to the users, they'll just put "next" on every single one, and that's all your planning and resource allocation…
-
I'm sorry, your requirement is not clear to me here. I really don't understand what the problem is.
-
If you don't archive them, then the list will continue to grow, and people will be able to use the released versions. The point of archiving is to stop people adding releases you aren't going to want to add to. I'd recommend using it as intended.
-
It probably can, but it won't be supported.
-
Ok, then you're definitely going to have to work upwards through thelog - where do the errors start?
-
That error can be caused by a number of things. Often, your version of java, but there's other causes. Could you work your way further through the error logs - you should be seeing a number of "caused by" after that line. Might be worth looking at the lines before it as well.
-
Cloud and Server are totally separate systems. I assume you are trying to run a Confluence server on one of your servers, or maybe even your own machine, which is absolutely fine. Yes, you can run it on a VM, but it's not necessary. It'll run on any machine that runs the right version of java and has enough power to…