Comments
-
All versions available on the standard download page are "stable". Atlassian release "Early Access" and Beta versions separately for those of us who want them
-
>Velocity/burn down charts These work entirely on the "definition of done", which, in Jira Software, means "the far right hand column". For Jira Software, the resolution is irrelevant.
-
My thoughts are that you've come up with a very good way of handling issues so that Jira works well for you. I would have a set of status in my workflow that show me where everything is and then build my boards around it. A developer board would be exactly what you describe - some columns showing "to do", "being developed"…
-
Ok, that's correct behaviour - it's giving you buttons that start transitions in your workflow. When there are more than two available in a status, it tries to conserve screen space by moving them into a workflow drop-down. (You can change this number if you want) The workflow editor is the only way to "build a workflow",…
-
Could you explain what you've tried with Script Runner's behaviours? It does not just "hide text fields", it works for all fields.
-
My guess would be that you hit the Jira Server docs, rather than the Cloud ones. It happens a lot (in both directions), and I also think it could be made more clear.
-
Ok, you're not going mad! :-) You don't get Systems Administrator on Cloud, it's restricted to Atlassian support only. You can't go above "Jira administrator"
-
Are you on Cloud or Server?
-
That tells us nothing. What "app" are you talking about?
-
Which "app"?
-
That looks like the database has become corrupted. Your only real option is to restore from a backup. I'd strongly recommend swapping to a proper database as soon as possible as well, as the H2 database is not supported and often fails like this.
-
Yes, one row per issue, whatever the type.
-
Try Admin -> Manage Add-ons There's an "uninstall" button under each add-on.
-
Yes, it is complex to recreate. That's one of the bigger reasons why people generally don't try to do it.
-
Have a look at the documentation. https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html specifically
-
Those are all users added by add-ons. You should be able to remove them like any other user, after removing the add-ons from your system (Admin -> manage add-ons should let you remove them)
-
To be fair, it's not a Jira limitation, it's an Agile one. Agile processes define only the last column as "done"
-
The first line of your error says it all: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Means simply that Confluence cannot get to the database, or that the database is not allowing the…
-
" Create with shared configuration" refers to sharing plain Jira schemes, not creating Software boards. You'll need to add the Scrum board manually.
-
Completely. Jira Cloud is one (increasingly divergent from Jira Server) Jira product run by Atlassian on their hardware for you. Jira Data Centre is Jira Server adapted to run on many nodes on your hardware.
-
It depends on the condition needed. In the question, the condition outlined is not one you can do with "plain" Jira off-the-shelf.
-
Yes, absolutely, use other fields (labels, user fields, etc) to indicate shared responsibility and/or break down tasks into parts which will have different single assignees.
-
The error you get in the browser doesn't tell us much, but it does tell us that Jira has tried to start up and run. In fact, it is running, because it's able to deliver that page! Albeit it's not running enough of itself to do anything else. There will be details of where it has fallen over in the application log. Look in…
-
That suggests that Tomcat is running ok, but it has not started the application internally. Check if it is Tomcat/Java listening on 8090 with a "netstat -plant" and then look at the Confluence application log to see why it's not starting (<confluence home>/logs should contain several logs, start with the…
-
Export your Pivotal data to CSV and import that.
-
To be accurate, you've fixed whatever was wrong with your download process, not "Atlassian changed published file". I've got a working 6.3.4 download from the day it was published and it's identical to the one I just re-downloaded.
-
Ah, sorry, I don't want to come across as a grumpy bear. But, I do get very very tired of a) people not getting it and then b) cleaning up the horrid mess they make because they fail There's absolutely nothing wrong with shared or group responsibility for something. But it is a very simple proven fact that it always fails…
-
It is not a fundamental law of nature. But it is a fundamental fact that it does not work. "There are plausible, high quality, competent management schemes where an issue is assigned to more than one person." - this is true, but only in two cases: * When the people are working so closely together, a mistake cannot happen.…
-
Ok, that call is working absolutely fine for me as well, with all three methods I tend to use for REST calls. I think you'll need to look closely at what your application is doing when it makes the call, because it clearly is not sending the valid data my calls are, or the ones you are using in Postman.
-
The answer for people with no ScriptRunner is "create separate workflows" SR people have another option - parallel transitions. Have two transitions that go from one place to another, with similar names. One should have the screen, the other should not. You then place a scripted condition on each - one that says "when team…