Nic Brough -Adaptavist- Expert

I have one, but it's written in quite an obscure language and an old database that you almost certainly won't be using (it's not quite ANSI SQL based!). You'd need to do a lot of translation. I would strongly recommend that you write your extract to fetch the data, parse it for what you need, and poke it into your database…

Jira doesn't track when you last looked at an issue, so, no, there's no data being trapped that could answer the question I suspect it's mainly because there are a lot of ways to do it - did you last look at it when it turned up in a report? A gadget? It's on a board you have open? Obviously a plain issue view will be…

A very British one - when mum says "pop into Bejam for some frozen peas on your way back"?

"knock the tab out to keep it"

There is a slight nagging doubt as to why you're not simply running the JSD on the Jira install so you wouldn't need an application link, but ignoring that doubt as it doesn't answer the question: You really need an admin to set this up - a Jira application link to another Jira won't give you any of the benefits of having…

This is exactly what it says it is - Jira can't connect to its database. You'll need to read the logs for more information on the exact error, but as you've had it working before, you're likely to find that the database server is down or unreachable due to a network problem.

Ok, then it may be that the gadget is tied to an application that the user does not have access to (if, for example, they are a Core/JWM user trying to use a gadget that is for Jira Software). If it's not that, then you really will need to read the logs for errors. I would try tailing the logs and getting the user to…

Don't think of a workflow as belonging to a team or project. A workflow represents the lifecycle of an issue, it's entire process. That would make the idea of "moving between workflows" nonsense, there's no reason to do it. It may well be that certain teams only work with an issue during part of its lifecycle, and you can…

Welcome to the community! You'll need to re-open the issues, so that they take on a status that is not "done"

Shouting at your sister to get off the 'phone because you wanted to use the internet "I was using the internet before the web existed" Still remembering your login to JANET "What's a search engine?"

I think you've run into https://jira.atlassian.com/browse/CONFSERVER-61145 - this is a bug in Confluence that only crops up when using older versions of MS-SQL. The fix is, I'm afraid, to upgrade MS-SQL, or abandon the upgrade until you can use a later version of MS-SQL

As you've somehow managed to get two copies running, it's utterly broken, and not able to respond to your shutdown commands. You'll need to maunally kill both of them, undo whatever it was that allowed you to run it twice, and restart one copy.

See https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Data-Residency-Comes-to-Australia-amp-Update-on-Data-Residency/ba-p/1825538

First check that the app that provides the gadget is installed, licenced and enabled in the Admin -> Manage Apps section. If it is, then you'll need to read the application logs to find out what is going wrong.

Could you explain what you are doing to install the app and where exactly the "page not found" happens?

I suspect that your "live" status is not in the last column on your board. Only the last column is considered "done" on a board, and if you move an issue from the last column back out to any other, it is considered "reopened"

Ok, so we'll need to see the list of issues in the sprint, only showing us the key (just so we can see it's one issue per line), the status and whatever you have selected for the estimation field, plus a shot of the header of the sprint where the numbers appear to be adding up wrong.

Sorry, I meant the configuration of the connection to the database - the error message is telling you the user does not have the right access.

Free trial won't affect the functionality. This does sound like one for Scriptrunner support - https://docs.adaptavist.com/sr4js/latest/get-help is the starting point

No, because the boards select issues they should see. You could add "and sprint is empty" to a board filter, but this does mean you won't be able to use the board as a Scrum board any more, because it will never display issues as cards on the board.

Is task a sub-task type?

Ok, the error says your database is misconfigured - see "Cannot use default schema name dbo on Microsoft SQL Server because the login schema of the current user (guest) is different and MSSQL does not support setting the default schema per session."

Yes, it's just jira, like I said. SysV is shorthand for SystemV, one of the startup frameworks that Linux systems use.

Actually, where and when you use them is up to you. What matches your process? If you don't want to use "tasks", don't use them. Assuming you have Jira Software, then you have three groups of types to think about: * Epic: only one issue type can take this type, and it is strongly recommended that you do not rename it *…

Ok, that suggests you chose an issue that doesn't have any data that needed migration. Next step would be to use bulk-edit to try changing a swathe of them from one type to another - try the first 50ish maybe?

Yes, you'll need to be scraping data over the REST API. See https://docs.atlassian.com/software/jira/docs/api/REST/8.19.1/ for the calls you can make

The issue link is by far the best way to do links between issues. If you do link issue-A to Epic-B, from issue-A, the Epic will immediately show the link without needing to be updated. But, no, it's not the same as an Epic link, and a story can only belong to one Epic.

Most of us just wouldn't bother putting the field on-screen. The request traps the reporter automatically, and if you need something different, it's easier to set it with an automation than bother the requestor with it. I don't think anyone using a system that asks for a login and hence knows who you are would be surprised…

Yep. It's actually because JWM is "the Jira Platform" - you can't run JSW on anything else, it needs all the stuff like fields, issues, workflows, screens, people, email etc that JWM provides. And the easy way to describe licencing is "A Jira Software licence includes a JWM licence for that person"

You can't really do this in plain Jira - the best you can do is report on how fields HAVE been used, and subtract that from a list of fields that exist. I'd strongly recommend looking at the housekeeping or migration apps in the marketplace, as they can easily report on actual usage. Project Configurator, Configuration…