Comments
-
Atlassian accounts don't necessarily have currencies associated with them, could you explain more about what you are trying to do?
-
No. Some of the permissions are a bit of a hangover from when there were no "conditions" on the workflow. The close permission used to mean exactly that, but now you have to explicitly use it in a condition in order for it to take effect. Essentially, the close permission in the permission scheme is nothing more than a…
-
You need to find or write an add-on to provide the listener, or take advantage of something like the script-runner add-on which allows you to write code for listeners inside the JIRA UI.
-
Code - you'll need to find or write a listener that can detect changes on subtasks and apply whatever your adding up scheme is to the parents.
-
Interesting, no, I don't think there's anything that would or should do that.I'd check the issue history tab first - that should record the sprint being entered and removed.
-
Sorry, what disappears?
-
Ok, for a global field, you can rule out projects/issuetypes which do not have the field. I suspect you might have a broken index for 50 issues, is it possible to schedule a full re-index? (Not background)
-
How is the field configured (global?), and what type is it? What does "custom field is empty" return? Can you see which 50 issues throwing the discrepancy?
-
Um, it has to be xml, or it's not an xml output and can't be read. If you look carefully at the files that are downloaded, you'll actually find they're named as office files already. I'm not aware of anything that would generate the files as though they had been saved by Office 2010, so I'm afraid you'll probably have to…
-
Yes, but you won't get a huge amount from the "connection" - you'll need to do some work to do anything more than basic linking.
-
You have a field called "Target NetAct Version" in your JIRA system. In that project, for bugs, it has been set as a mandatory field - you must enter data into while creating an issue. So you need to fill it in. The next logical step is that as you're asking here, it probably means you have already tried, but you cannot…
-
Um, you can't really do it. Pro fields provide project fields. Excel exports are of issues and their fields. I don't have an installation of Profields to hand, but I know it doesn't do a direct export yet (i.e. list of projects plus all their fields). What you could try is defining a filter that exposes one issue in each…
-
See https://docs.atlassian.com/jira-software/REST/latest/#agile/1.0/sprint and have a look at the "update" call which starts sprints.
-
It looks like the python-JIRA API is sending data that JIRA does not need or expect. Have you tried making the call over the REST API (this is what the python wrapper calls, so it's worth checking if that gives a similar error)?
-
Yes, that's what the blog says.
-
Please have a look at the article given in the earlier answer.
-
It's been removed, as per the link I gave before.
-
Ah, ok then it's valid because that part of the paid addon is there. I've not used the direct urls before, so I thought it might be part of the old addon that is going away. Sorry!
-
Bear in mind that this will probably be removed soon, as covered in the blog.
-
My guess is that you were using one of the gadgets that were removed from Cloud a few months ago. Specifically: https://confluence.atlassian.com/jirakb/jira-timesheet-reports-and-gadgets-removal-from-jira-cloud-792504481.html
-
You are misunderstanding what a board does. Projects contain issues. A filter returns a list of issues, often with a simple "project = X", but they can be much more complex, with things like "project in (x, y, z)" or "issues assigned to me" or "project in (x, y) and issue type = bug". A board is a view of a filter. So,…
-
Ah, no, the catalina.out is telling you why the app isn't starting (it is starting, but not fully) You'll need to work out what this is, and fix it: SEVERE: Unable to create directory for deployment: /opt/atlassian/confluence/conf/Standalone/localhost Probably permissions, possibly disk space/quota, but could be something…
-
Hmm. I see what you mean. That log is way too short and unhelpful. Could you have a look for "Catalina.out" as well? That's the Tomcat log, it might tell us some more.
-
There is more before and after that segment in every log I've ever seen. Except in the case where a plugin was silently killing Confluence dead, but in my case, I'd had it running well enough to install this dubious plugin, and I don't think you could have got that far. Are there ANY warnings or errors outside the block…
-
What does the application log file say?
-
You should log into your account on my.atlassian.comand change the card information there. If you're struggling with that, you need to get in touch with Atlassian via either OnDemand support or possibly sales-at-atlassian-dot-com if it's not OnDemand.
-
I've done that a couple of times. It's completely harmless, with the caveat you have already mentioned. When upgrading in place (pointing a 3.1 Confluence at a database that was behind a 2.9 installation), it fell over on the new indices. A real DBA did give me an explanation at the time, but all I can remember was that if…
-
Ah, good. Sort of. That query is not structured in a way that might be causing a problem. Straight clauses joined by "and"s are almost always straightforward. So, now we need to ask you to test the effects of re-indexing
-
You don't know that indexing is the problem yet. It could be the structure of the query.
-
Sorry, obviously not enough coffee this morning.