Nic Brough -Adaptavist- Expert

You can edit the workflow to change this, but you have a bit of a problem. The "draft" workflow editor has a long-standing flaw which stops you creating transitions from status that don't have already have one exit transition. (Also, darft won't let you delete status) Your best option therefore is to take a copy of that…

You've let the MS-SQL server run out of space. See https://confluence.atlassian.com/jirakb/jira-server-fails-to-start-with-full-ms-sql-transaction-log-error-388399950.html and then, to fix it,…

Permission schemes are accessible through the project configuration area for classic projects. Next-gen projects have a concept of "access" in there. See https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/

A Jira Service Desk already is a Jira project. Before we talk a lot about synchronising two projects, it's worth understanding why you might want to do this. Why are you not configuring the JSD project to send the emails you want?

Jira has a simple user service built into it, called "embedded crowd". It is a very cut-down type of Crowd, but it can be used by other servers. Those other servers however, need to be written so that they can use an embedded-crowd as their directory server. As far as I am aware, Atlassian Software (Confluence for example)…

* Start by defining what is "done". Is it done when it goes into QA, or after it passes for example? Once you have a clear definition of done, related to status, you can put all the "done" status in the last column, and your sprint reports will give you the reports. * Probably by filtering for "current sprint" and "done"…

My guess is that when you say "title", you mean "Summary". Try {{issue.summary}} instead of title

Because Jira has a simple resolution flag - if the field is filled, the issue is resolved. If it is empty, the issue is open.

That sounds like you have a broken resolution. You have a resolution of "incomplete" in the list, but it does not mean what it says. When you put any value into the resolution field, you are marking the issue as resolved, whatever that value might look like. To fix this, you need to change your workflow such that when an…

Ah, sorry, I thought you were talking about presenting the UI in Russian, not the documentation. As far as I am aware, Atlassian have not written much of their docs in anything other than English.

You'll need to change your setup so that it uses a valid supported version of Java.

I agree with this - you've got a situation where "done" differs between two separate teams. You can make your workflow match the actual process, and then set up boards for each team, having "their" done mean the right thing for them. My over-simplified example is when you have Development and Test teams separately. You…

There is no good way to do this. In theory, you could replicate the database over to another place, and point another instance of Confluence at it, but that Confluence would have to be read-only, and you would have to restart and re-index it every time something was replicated. I cannot find any tools in the marketplace…

No. A link is a simple record of connection between two issues. It does not do anything other than show the human that there is some connection. You can, of course, use the links for all sorts of things, but there is no off-the-shelf function for "update issue at the other end of a link". You will need to do some coding or…

Could you explain what this has to do with Atlassian stuff?

I am not sure "go to your profile and select your preferred language" is "very complicated"? Could you explain why you think that is is complicated?

The best way to do this is: * Create a new, empty database * Install 7.5.2 on the new server and point it to the empty database * Make sure that runs ok, just for the default admin user you create * Stop the new install * Overwrite the new database by restoring the backup over it * Restore the attachments directory on the…

There is no way to do this. The last column on a board is "done", and hence gives you a burndown. Your goal here is perfectly valid, but botching status so that things are done but not done is not the right way to achieve it.

Ok, so you have not really "closed" those issues - they're not in a status that the board that the sprint looks at has in the last column.

What do you mean by "notification in the Jira dashboard"?

You will find the database slower and a lot more fragmented than the APIs. "Read an issue" for example is one single API call, but would need 18 joins in SQL just for the basics, going up into the hundreds for a more customised Jira system.

There's no way to "automate" this, you are mostly describing "use a page", which means reading it and looking at its setup and history. So to answer your specific questions: * Read the page * Read the space permissions and restrictions on the page * Edit the page * Use the archive function These processes are as automated…

That "mapping" is done in the application, not the database, so you will not find it with SQL. You should stop reading the database for this and try to use Jira properly

You will need to correct your code such that it sends data Jira can understand. An empty response almost always means you are sending something in the wrong way.

Technically, yes, in real life, no. Whilst the backup is xml and hence theoretically readable because it contains everything, it is very hard to read, without huge piles of code. I would say that it's only suitable for importing into another Jira, not as an archive.

Whatever version you choose to use, although I would check what version is most compatible with Jira 8

We can't. We have less access to, and less knowledge of, your system than you do. You will need to talk to other people who use your wiki. I'd start with the person who asked you to use it.

The issue prefices are nothing to do with the board, they come from the projects that contain the issues (boards are a view of a selection of issues, not a container for them like a project is) The name of a board is not that important either, it won't do anything if you give it a duplicate name. If you are seeing sprints…

A well formed html document should only have a single header, type, body etc, and your code is injecting others into the body of a page. Most browsers cannot cope with this and a typical response to a broken web page is to simply stop rendering when you reach the bit that is broken. You should remove pretty much every line…

Issues will go into the next sprint if they are not "done" when you end the current sprint. (And for issues with sub-tasks, they can only be "done" when all their sub-tasks are done as well) Jira only recognises the last column on the board as "done". The database is a terrible way to try to query this stuff, what you…