Comments
-
If a story and all its subtasks are in the done column, then the status based quickfilter I mentioned should do it.
-
I think we should step back and revisit some of the concepts here. My usual starting point is to separate board and project. A project contains issues. A board is a view of issues (possibly from many projects) Every issue has a workflow. A workflow is a collection of status which an issue might be in. To change from one…
-
The "version" thing is a very Kanban thing to do, but it does not quite suit you as you're using the board. I have a feeling you have misunderstood the "release" process. This takes everything that matches your definition of "done" and sticks a Jira version on it. The board then ignores it because the default board config…
-
I am sorry, I do not understand that. You asked about a problem that happens during move, although it is not clear what the problem was (not from you, but what the previous admin said did not make a lot of sense) I have tried to explain what a move does and when it asks you for more information, and I think you understood…
-
You can grab add-ons from the marketplace directly. Have a look at the dev environment and make a note of the *exact* version of the add-on you are happy with in there. Now visit https://marketplace.atlassian.com , go find the add-on, make sure you're looking at the server version and click "versions". Find the matching…
-
You can stay on 7.6 if you want, it has been fixed there. 7.7 will include this fix.
-
Set up a quick filter for "status in (<your list of closed status>)"
-
There are good reasons for not using h2 in systems you might want to run as a trial or development - it doesn't scale and it can fail without warning, and when it does, it usually fails catastrophically.
-
I can't think of any other way to do this, unless there genuinely are no transitions out of the status
-
There's a quirk here that I think we're missing. This is going to sound very odd, but it comes out of two things - the code is easier, and it gives you a flexibility that some (rare) cases need. I think you've got the security and visibility of existing issues right, and I think you understand it in full. The confounding…
-
To be explicit, Fadoua is asking you to check the "All" transition that goes into QA (the "all" means it comes from all other status, but you get a hard-to-read spider web if you draw them individually, so "all" is a neater way of showing it)
-
The community likes to learn and accumulate knowledge, rather than delete. There's probably several people who are having, or will have the same problem, so a quick description of what it was would be very welcome!
-
That's the only way without the Field Security add-on (Behaviours can do it, but it only protects it on the client side and imperfectly)
-
There's a grey tick to the left of answers - click that to mark the answer(s) you found most useful.
-
Very much so. Merging on to Cloud is fraught with issues, depending on what route you want to take. If you want a full proper merge (keeping history etc), you'll need to download your cloud data, upgrade the server, merge them on server then export the merged data and use it to overwrite your whole Cloud system. A lesser…
-
You'll need an add-on, as Confluence is a web-based editor and not a form collector. Try Adaptavists "Forms for Confluence" and "Confiforms" as the well-established options on the marketplace.
-
No, there's no way they can say that. They have no control over the servers or configuration that company who has installed Jira are using. It's up to you to determine that on your hardware.
-
But there's nothing to investigate. You ask Jira to move an issue, Jira checks the data is valid for the target configuration, asks for updated data id it needs it, and moves it when it has valid data.
-
So this is not a move of Jira from Server to Cloud, but a merge now?
-
No. The best way to implement forms in Confluence is via macros. It saves having to build an entire editor in a system that already has one.
-
I assume you mean MS-SQL 2016. The answer is "no", that is not supported. See https://confluence.atlassian.com/doc/supported-platforms-207488198.html
-
Are the instructions you are looking at for the same platform you are using? Server or Cloud? Their interfaces are very different
-
Indeed, it must be an optional field for the target. If you made it mandatory, then the move would start prompting you to enter it for issues where it is currently empty.
-
You will need to buy the new Cloud address, then migrate to it. See https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-one-cloud-instance-to-another-cloud-instance
-
I think what you mean is that you have a Server Jira install, and a Cloud Confluence. You can NOT "migrate" a Jira into a Confluence, they are totally different systems, with totally different data. But if you want to stop hosting Jira, you can * Buy a Jira Cloud (in the same atlassian account that owns your Confluence) *…
-
In Agile, you burn down on "done". Jira Software defines this as "the last column on the board". There is no way to use other columns.
-
You do not configure the move operation. The move operation scans for differences in the configuration between source and target and makes sure they are minimally compatible. If something is compatible, it does not ask or perform any migration or update because it doesn't need to.
-
There is an active Confluence pointed at your database, so it is running it. The Confluence showing this error message is a second (or third, or more) one that is trying to use that database. This cannot be done - the first Confluence running puts a lock on the data to prevent any further instances of Confluence from…
-
This can't be done. Confluence and Jira are two totally different systems. The data for one is nonsense for the other. Please could you explain what you're actually trying to do? Change the hosts for each of the two systems?
-
I'm afraid I don't understand. You already asked that, and I told you that you'll need to work out what KPIs you want from it and then monitor it.