Nic Brough -Adaptavist- Expert

Yes, each installation needs its own database. (Not database server, just database - it's not uncommon to see Atlassian services all using the same database server - I've got one Postgres service running several databases, one for Confluence, one for Jira, Crowd, Bitbucket, etc)

Yes, Jira will go back to ordering those two by the default order.

Stop trying to do this with SQL, it's a nightmare, the database is absolutely not designed for any form of reporting. What problem are you trying to solve with this extract?

Jira does not have this by default, you will need to add a custom field for it if you want to do it as a date on issues, or configure your SLAs to show you the data

That segment of the docs is slightly misreading - there's no need to check workflows validators and post-functions if you're removing an inactive workflow. You do when you are removing a custom field - validators and post functions will fail if you delete a custom field they are using.

Your two projects appear to be different types - one is software, the other work management. Work management project boards are not configurable, they draw their config from the project, that's why you're not seeing the settings in there.

I would focus on this bit: >The status is DONE. There's no resolution field Status is DONE looks totally right. Status is oddly simple (but still manages to confuse people a bit). The resolution "field" though matters to most of the rest of Jira. Could you open up one of the issues that looks wrong, check the status, its…

Yes, absolutely all of those things (with variations). With a huge caveat that I am going to talk about my Atlassian experience from 2004 to 2013, when it changed because I joined a partner company, and stopped really working with day-to-day users. TLDR: Always form a group of leaders who can define and drive the way you…

No. We will not know until Atlassian announce it formally. We can guess a bit though. The cadence since Atlassian started doing LTS releases seems to average out at 15 months (I couldn't see useful patterns in release numbers) 7.13 was August 2021, so I don't think we'll see a new LTS release until we're heading to the end…

That particular problem was fixed before Cloud diverged away from server, over 9 years ago. If you are seeing problems that look the same, I think it needs reporting as a new problem (yes, maybe as something that's come up again). Could you provide more detail in the symptoms you are seeing now? As the old one was fixed,…

Welcome to the Atlassian Community! I would suggest that someone changed a board config, project, or workflow in a way that made the old issues no longer "done" Open one of them up, and check the status, its resolution, sprint, and what boards it might be appearing on to start with.

Ok, that makes good sense. Strictly, it's not "agile" - you're supposed to have the thing delivered by a single cross-functional team, so Jira, as an Agile tool, doesn't easily support it, but you can do it. First, you'll need a model of the workflow for any story. There's a long discussion to be had about that, and even…

You don't - currentUser() means "the person running the filter"

Welcome to the Atlassian Community! Could you give us some more information? Starting with what this has to do with Atlassian software?

Welcome to the Atlassian Community! I'm afraid that means the file that was uploaded to Bitbucket was corrupt. You'll need to talk to the person who added it to Bitbucket to get a corrected version.

Welcome to the Atlassian Community! Ohh, yes, I've had this too, not just with Trello. Lastpass is definitely a little bit enthusiastic about filling fields and sometimes jumps on the wrong one. Try firing up your Lastpass vault, and finding the Trello entry. Open it up in, and look towards the bottom. The "nuclear" option…

I don't think I needed a screenshot, just the new description has triggered a thought. For fields to come out in different columns, they need to be different fields. I am pretty sure you have set up your projects to use different fields. All called "work time", sure, but different fields. You can easily do this by…

Welcome to the Atlassian Community! There's a whole cloud of options I almost started an essay on, here, but I'll try to stick to just fixing your problem! You can leave the setting as "show all" and then look again at the "sub filter" that's hidden behind the pop-up box. You could add "and updated < -8w" to that filter.

Welcome to the Atlassian Community! You don't. Confluence is not an artefact storage system, it is a structured wiki. It does have simple storage for blobs, you can attach things to pages, but it is a simple flat list of (versioned) attachments per page, there's no use for "folders". The "tree structure" applies to…

Welcome to the Atlassian Community! Actually, that question does have the right answer, but it's missing a load of context and there's no explanation of the underlying problem. The short answer is, as Dave said Use the "add sub-task link in the 'more' or 'tools' menu on your Story" However, the context here is that this…

Yes, that's correct. You'll need to add a new subtask type for "task" after renaming the existing task to something else.

We can't see your systems, we have no access. Could you give us a screenshot like @KAGITHALA BABU ANVESH gave us?

Yes and no. * Jira can have up to four "types" of account. * Jira user - can use Jira Core only, creating issues in Jira projects (Jira Work Management or Jira Software) * Developer - a Jira user who can also use Jira Software functions (boards) * Agent - a Jira user who can also act as an Agent in Jira Software Management…

This means you have not got the right SSL certificates installed on your Jira. You'll need to get the certificates your LDAP server expects and install them in the java keystore the Jira is using.

Are you sure the "assignee" the automation is looking at is the assignee of the sub-task? Is your automation setting the assignee and trying to send the email at the same time?

Boards are a view of a selection of issues, not containers for issues. If you want to see issues on a board, you make the board select for them. There's no "move issue", and you definitely don't want to be copying other issues because that splits the story Take a look at the board filter. How could that be adjusted to…

It's sorting alphabetically, not numerically or by date. Alphabetic sort does not understand dd-mm-yyyy. Nor does it understand US dates (no sort gets that right without having to be coded for the wrongness), but it will work for yyyy-mm-dd, so try using that as the prefix format.

The "applied to" parameter field there is listing projects, to add one, start typing, either the name of the project or the key, it will auto-suggest for you. I do not understand what this has to do with a script or variable within a script.

This won't work - Confluence considers each directory you configure as a different source. So even if they are the same, "directory 1: nic" would not be the same user in Confluence as "directory 2: nic" You can't use Confluence's directories for directory fail-over (yet) You need to do one of * Implement failover recovery…

Ok, that rules out a couple of things that can be an issue here. Date picker fields should be selectable here (and work fine for me, with a simple plan), so the problem is one of three things: Check the setup of the Deadline and Release Date fields - go to Admin -> Issues -> Custom fields and find the field, then click…