Nic Brough -Adaptavist- Expert

They can't delete the configurations, as they may have been used by other projects, and you might want them for audit purposes too.

Yes, and you've used the wrong one. Why did you ignore the supported versions doc you read?

I don't understand the first part of your comment. Do you have a question about some part of what has been said before? Making a statement that uses some words from the rest of the conversation doesn't tell us anything about what you are looking for from the conversation.

That is not the area of the log from when the error occurred. You need to read the log at the point at which the error occurs, not just read the end of it - the system is doing other things and logs them too.

Have a read through https://confluence.atlassian.com/conf74/confluence-release-notes-1003129799.html and then skim the same for the intermediate releases.

You do not. Post-functions are actions Jira takes *after* a transition has occurred. They are done because the transition has been requested. It's too late to "restrict a transition" when you get to post-functions - the transition is complete by the time you get to them. If you need to do stuff that might fail in a…

So you have only a $10 licence?

>is there any way an end user can see all link types and names. Yes, they will see the list as soon as they try to use the link function when they start to think about linking issues together. >Is there any JQL query or any other approach to do so? JQL has some functions that look at links, but you can only search on real…

I would keep it simple and try to use the built-in functions. Go to the page you want to copy over to the other Confluence. Go to space tools -> content tools -> pages -> export -> xml -> next -> export tools. Select the page(s) you want to copy and hit export. Import that xml into your target system and move the pages it…

Ok, so this is going to sound bad or grumpy, but I am trying to avoid a rambling essays: You have found and read exactly the right documentation that you should. And you've not just followed it by rote, you have understood it too. So why have you installed an old and unsupported database at the back end? Azure can provide…

"issueFunction" is a search trick provided by the Scriptrunner app. It is not a part of Atlassian's base Jira product. I'm going to be a bit brutal here, but hey, Atlassian says "Open company, no Bullshit, so I'll try: * I work for Adaptavist. I'm a Consultant, not a Scriptrunner product person, but feel free to assume…

Atlassian haven't supported SQL Server 2014 for their products for quite a while. It does, as far as I can tell, work ok for Jira 8.x, but it is unsupported, and you should upgrade it to a supported version as soon as you can. 2016 and 2017 are supported as the databases for Jira 8.12, so I would recommend upgrading to…

I am sorry, but no, there is no function for this (yet) You have to work through it manually, but there is some help - in a lot of the admin sections, Jira does at least group things into "active" and "inactive". To do the housekeeping, we admins can at least go into those lists, expand the "inactive" section and then…

Check the permission scheme for the project - is this user in a group/role/etc that has been named for the "assignable user" permission?

Ok, so that has nothing to do with the database, it's a problem with reading and rendering. What are you doing to provoke that error?

Search for something like "due date < +3d", save it as a filter and subscribe to it. It will email you a list of matching issues at a frequency you choose. The < means "before" and +3d means "three days in the future", so that filter will give you "all issues with a due date before Sunday" (because it's Wednesday as I'm…

Confluence does not have any content scanning functions that would allow you to prevent the posting of words you don't want. Profanity is usually something you should take up with your authors who are doing it, not try to filter with code. I can construct incredibly offensive stuff without profanity too, stuff that will…

Yes, but it's not pretty. See https://confluence.atlassian.com/jirakb/merge-multiple-instances-of-jira-cloud-779160767.html

It is not directly recorded. The best you can do is rather convoluted process and it's 1-by-1, so slow as well. For any given workflow, * Pull up the diagram for it and write down every possible status change as a "from x to y" statement * Look at the list of projects and issue types if you want to refine it configured to…

Ok, two more essays that show a lack of understanding miss the point. Let's get back to the basics. >Wednesday is not green. If we want a boolean answer, it's False. That is only one of the four answers, but you've also changed the question by phrasing it that way. To show that you're understanding the underlying logic of…

@Philip Couling- Since when was null = 0? "Labels do not apply here" is not the same as "There are 0 labels applied to me" Have a think through the question "is Wednesday green?" - hopefully that will help you understand it. You'll need to work through all four possible answer categories to get there. I'd also recommend…

Yes, it is "misleading", for humans who make incorrect logical assumptions. It's natural, it's how we think, even those of us who have a lot of experience and try to think logically fall back on fuzzy logic by default. But it's still correct. And changing it to meet our failures is not useful. In fact, it would be a…

I can't see a logged issue for an XSS attack on 6.4.9 specifically, but there are a few for 6.x that you might want to read through to see if there is something you can patch in. However, the recommended solution/patch for all of those vulnerabilitues is simple - upgrade to a supported version. The lowest supported version…

@Philip Couling- apologies, our postings crossed over, so my last comment was written before I'd seen what you've said. I completely agree that "labels != something" fails the principle of least astonishment. Unfortunately, there's a lot of logic that does. Humans are notoriously bad at logic, and clarity, especially when…

Ok, they're still more sets of rules than operators, but they are closer to queries. Remember that a search is a search for a set of issues, it is NOT the report on what data you get back. * Label in (A, B) * Label = B * Label not in (A, B) or label is empty * Label != B or label is empty * Not a query, that's a question…

You'll need to read the history for each individual issue. It is logged as a change of type, with date, time and author, but the search in Jira does not yet have functions that can search the history in full, only bits of it.

This would mean that your sprint includes the stories in the other project. Sprints are not project objects, they belong to boards which can select issues from many projects. You'll either need to amend your sprint so that they are no longer included, or accept that they need closing or moving to the next sprint.

You will need to create an app to provide a new field type. See https://developer.atlassian.com/cloud/jira/software/modules/issue-field/

Yes, you need to take these manual backups if you want to backup your projects. Restoring the download will indeed scrub over all the content in the system you restore it to. If you want to restore a single project, you'll need to restore that download into a temporary server system and merge the project back into the…

Yes, you did mislead us with the labels. I would use the REST API to get the tags. The database is the worst possible way to try to find that (especially as you'll need to look in many places)