Nic Brough -Adaptavist- Expert

It's not a scolding, it's more a case of explaining that they're using a scrum tool for their non-scrum processes, so there's going to be issues. In this case, they're not doing the estimation in the way Scrum expects. So: >What does rolling into the next sprint mean? It means the entire story is placed in the next sprint…

What have you tried to do to fix the problem? Restored from a backup?

What "issue"? Jira lets you share your issues, so everyone can see the problems. What is wrong with "client A has a problem, not sure B does, but let's be open that they do"?

Your description of what you're trying to achieve is screaming "cascading select list" to me. Jira has these off-the-shelf, no need to mess with Behaviours or any other complexities. If cascading select lists are not right for you, could you explain why?

You do not. In a Scrum methodology, you are supposed to complete a story in a single sprint. If you can't for some reason, then the issue rolls over into the next one (or goes back into the backlog), but you should never be planning for that to happen, it represents a failure to achieve what you said you would do. If you…

Ok, welcome to the world of Atlassian Administration! The log to start with is in < confluence home >/logs and is called atlassian-confluence.log - that is the main application log which usually records most errors. There may be other files in that directory with errors as well, for some problems. If Confluence is not…

Any of the ones you can find in the marketplace will do - you'll need to evaluate each one to see which is the best fit. Jira doesn't do it because you shouldn't really need a template to enter an issue.

You'll need to install one of the templating apps in order to do this. Jira does not have templates off-the-shelf (as you shouldn't need them - the desire for a template implies someone has over-complicated your issue tracker), so you'll need an app to do it. Same with "private fields" - Jira is intended for collaboration,…

As above, check the permissions on the database files and correct them if necessary. If it's not the permissions, then you will need to go bak to a backup because the database is corrupt.

It doesn't do anything other than show up when someone looks at the project header.

Ah, ok, I see that now, but I don't understand why you've suddenly changed the subject from one system to another. It does not help that the error you are seeing in Confluence can be caused by the same problem you have with your Jira - I have conflated the two together because both problems you are talking about now could…

The database file is the one given in the error message (with h2db in its name) The SQL error you are getting is there because your database is corrupt

Sorry, my last comment crossed over with your posting of the log you actually needed to show us. So, yes, that's pretty clear. Your Jira is configured to use the dev/test h2 database rather than a proper one for any serious use. h2 is a file based database, and Jira reads the files from it as it starts up. For some reason,…

Welcome to the Atlassian Community! It's impossible for us to know how they would prefer to be contacted, or who they are. I would ask other users of your Jira around you, the people who granted you access to it, or the person who told you to use that Jira. 

You will need to talk to the administrators of your Confluence system - they probably need to read the log files to find out what has gone wrong. Deberá hablar con los administradores de su sistema Confluence; probablemente necesiten leer los archivos de registro para averiguar qué salió mal.

Welcome to the Atlassian Community! I'm afraid posting an error message with no context and no explanation of whether you have done what it suggests you do next is not going to get you any help. Please tell us what the problem is, and what you have tried to do to get past it (like fixing your browser extensions or using a…

You need to find the part of it where it says it can't connect to the database.

I've not heard of any Atlassian app called "power automate" I'd suggest you start with a look at Jira's built-in Automations if you're looking to automate things in your Jira.

I'm intrigued about why! What use is only part of the key of an issue? I can't think of a use for it (well, a few migration contexts, but only to compare with existing data, which isn't something I'd use Automation for)

Ah, yes, that makes sense. It's not something that obvious in Jira until you get used to it, but the issue type is a very important structural item, and all the config for issues hangs off it. You can only use a simple "edit" to change the issue type when the source and target issue types have similar configurations -…

Um, so why are you using a Scrum board? The whole point of a Scrum board is that you timebox the work into sprints. I would swap to using a Kanban board if you don't want to use Sprints.

Welcome to the Atlassian Community! I think we're going to need some more context. Jira does not have a SOAP API, nor anything I'd call a "worker", or details about the worker. Could you explain what you are trying to do with Jira Cloud here?

Welcome to the Atlassian Community! It's because you might want certain things to behave differently. The issue type tells Jira how you want to handle issues of that type. It's not uncommon to handle stories, tasks, bugs, defects and sub-tasks differently, no matter what level (issue or sub-task) they are at. You can't…

Welcome to the Atlassian Community! Could you explain what you mean by "isle" here? The word does not make sense in this context. (Unless you really are asking what island or continent the Trello servers are on?)

In another thread on the same topic, the last suggestion was to simply forward any spam email (with as much of the email header detail as you can include easily, and no need to comment or complain) to https://www.atlassian.com/trust/report-abuse I think that's still the case, but Andy will correct me if it's changed…

Ask your questions here - that way, you'll get more attention from people other than me. What does your log file tell you the problem is?

Ah, it's not the filter then. " it should only display the Active sprint i.e. Sprint 51 but the results are displaying the closed sprints " This would be lying to the users though. An issue that is drawn into sprint 49, then rolls over into 50, and then 51, is in all three sprints. It's useful to know that, and a report…

Well, actually, that Raspberry Pi I mentioned 5 years ago is now handling 2,500 users, serving as the directory for a near complete server stack of Atlassian services.

The hierarchy in Jira Software is: * Epic * Issue * Sub-task You can have different "issue types" at the issue and sub-task levels, and it is not uncommon to see places that have structures like: * Epic type: Epic * Issue type: Story, Bug, Feature, Task * Sub-task type: Sub-task, Technical task, Docs So, using those three…

Yes, get an administrator to add it to the screen you need it on (create/edit/transition for the Epics)