Comments
-
Welcome to the Atlassian Community! How exactly are your people using the "Jira original archive function"? What are you doing to archive an issue?
-
The search might not be finding the filter, or it might not be shared with you. Have you tried finding the filter from Issues -> Search -> Manage filters? If so, and you can find the filter you want, can you try copying and pasting its full name into the saved filter box?
-
I think I can explain that - sub-tasks are only part of a backlog when their parent issue is part of the backlog. When you converted the Story to the Epic, you didn't orphan or disassociate any sub-tasks, but you did change their parent issue to be an item that would not go in the backlog. So they fell out of it. I assume…
-
You can't do that either, the default values can only be set to text
-
The "header" it's referring to is actually part of the page surrounding, rather than the body of your page (content). It's a result of support for the "unmigrated wiki content" being removed from Cloud. To have got that in there, your page was probably originally written on a Confluence server that was upgraded from a…
-
The Data Centre versions can use AD directly, the Cloud version requires Atlassian Access to be connected to your AD
-
What makes you think you want to do this with Automation? (You can't by the way, Automation automates things, it does not replace workflow actions in front of a user)
-
The status colour (category) has nothing to do with it. It is purely the current assignee and the resolution. In your case, my guesses would be either someone has added a second resolution field, or your index is damaged.
-
Welcome to the Atlassian Community! My guess is that it is working fine, but you were expecting issues with no label to appear as well. "Not in" can only work with labels that have a value. Try project = SF AND issuetype = Task AND (labels not in (KDD) or labels is empty)
-
Rsync for some, dedicated backup tools for others (I don't have to think about it, it's managed hardware)
-
I don't know what part of "yes you need to back up your attachments" I can explain more. You should use a tool that works best for you. Your mention of rsync (incremental) is probably the most simple and well-tested way to do that already.
-
The error message says there's no access for "SSL off", and that line you've got is for SSL connections. This suggests that you have not configured Jira to connect over SSL.
-
What user name are you trying to amend? What type of account are you using to log in? Google, Atlassian Access, or the default Atlassian Accounts?
-
Edit the workflow, specifically the transition - change the "transition screen" to one that has only the fields you want to ask the users for, or to "none" if you don't want the popup at all.
-
Nope, Atlassian accounts are separate entities, and they are only one of the ways of doing user accounts in Atlassian products. Server and Data Center Atlassian stuff doesn't use them at all. Cloud can use them, and it's the default or "internal" user system, but you could also use Google accounts or Atlassian Access. The…
-
This is a horrid query to construct, as you'll need to join at least 9 tables together in a horrendously inefficient slow query. The database is the last place you should be looking. Can you explain what problem you think this report would help you solve? It sounds like you want to do some housekeeping and simplification,…
-
"Inactive" is a display flag, not a setting, it's trying to tell you that the workflows in that section are not in use anywhere. To make a workflow active, you associate it with one or more issue types in a "workflow scheme" and then go to the project where you want it to be active, and change the workflow scheme the…
-
It is important to understand that there is no "duplication" here - boards are a view of a selection of issues, not containers for them. What you're seeing here is four different views of a single issue - all four boards are showing you the same thing. By editing the queries for the boards, you are simply changing what…
-
Welcome to the Atlassian Community! I suspect you are not using Atlassian accounts to get into your Company Confluence, and you don't have an Atlassian account for your work address (if you did, the "sign up" screen there would have said "there's an Atlassian account with that email, please log in with that") I'm afraid…
-
I already said you'll want to take backups of the attachments.
-
Atlassian accounts don't yet support multiple logins properly everywhere they're used, so you will have to log out of the community (there's a logout function under the profile menu, your personal icon near the top right of the screen), then log in again with the other account. Or you can use a different browser or an…
-
The pg_hba.conf file does access control. When your connection from Jira is trying to read/write the database, the postgres server is refusing access because the pg_hba file does not have a rule that lets your user into iit. You need to add a rule to the pg_hba.conf file to allow your user into the database.…
-
Yes, you can.
-
Welcome to the Atlassian Community! This is what it says it is - the user your REST call is logging in as does not have permission to see the issue or it does not exist (Or your user is not authenticated, and anonymous access is off, so you have to log in to see issues)
-
You should use whatever tools your administrators support. Most of the systems I help out with use the native database tools to take regular backups of the database, and have the attachments on a shared and backed up disk. The more advanced one replicate database and disk to other redundant servers so they can get the…
-
No, it would not. A sub-task is a part of a whole, and it's would make a nonsense of your issues if you can only see and work with part of one. That's exactly the opposite of what Jira is for.
-
Automation can fill in a field if you want it to be filled in no matter what, but it is not a validator or field configuration. It automates things, not controls process. You will need to do this with a validator or field configuration.
-
No, you need to add access for Jira to the file.
-
It is on your side. The url you gave us is for self hosted server or data centre install, so you will need to talk to your admins about it
-
This is not an error in your Jira settings, the pg_hba file is access control on the database. It is saying you need to add access for Jira to that file on the database side.