Comments
-
Those two filters are built in standard system filters and can't be removed
-
The backups take everything, but there's no way to get just the queues or filters out of the backup.
-
This is not a visual composer forum. I think you need to ask this somewhere else.
-
Ok, Cloud accounts are Atlassian accounts, which cannot be updated over REST. See https://confluence.atlassian.com/jirakb/user-management-rest-api-changes-in-jira-cloud-858756548.html
-
Yes, the backlog is part of the board. If you don't want them in the backlog, you're also saying you don't want them on the board.
-
This needs to go to https://support.atlassian.com/contact so they can look at the logs and explain which entity is throwing the errors and how to fix it.
-
That all looks fine, the only thing not shown is that the project is using that particular permission scheme. I'd also try the "permission helper" at the top right. But I doubt it will tell you anything you haven't already checked. As I said earlier, as this is all correct, it'll need to go to Atlassian.
-
Hmm. It looks good to me, so I don't think it's your config. Two other thoughts - 1) Can you try "sudo netstat - plant" to check that it really is apache listening on port 80? 2) In your apache config, how is Plesk configured?
-
Ok, it's not a proxy then, but Confluence is unable to talk to Synchrony for some reason. What do the Confluence logs say when you click "edit" on a page and get the "nothing happens" symptom.
-
Ok, that's good, it means it's just your atlassian-plugin.xml that is wrong, and not announcing the fields to JIRA.
-
What does the permission scheme for the project say?
-
You can't - as the error says, you can't (yet) maintain user access via REST on Cloud.
-
Looks ok, so it's probably the proxy.
-
It's not because the ranks are not numeric, they're an indication of the position of an issue in the global rank order, relative to the issue above it and below it.
-
The only thing that I know of that will hide the "create version" is the permissions. If they are correct, then you'll need to raise this with Atlassian as something somewhere is very wrong. Your screenshots imply that you do not have admin in that project.
-
So someone has changed the permission scheme.
-
The release button releases all the issues in the last column, and hence removes them from the board. That's the whole purpose of the Kanban release process - the issues should not be shown on the board when they're released. Of course, you can modify the board filters to work differently, but the release button is still…
-
It looks like you do not have project administration rights.
-
Ok, you'll need to read the logs to find out what it's doing and where it's going wrong.
-
It's an add-on one of your admins installed and tried out. If you're not going to use it, you can remove it. Not able to create projects or close tasks is almost certainly unrelated. Are you getting errors when you try to do these things, or are the options not appearing? (Remember you have to be an admin to create a…
-
Your proxypass and proxypassreverse lines are wrong. The first one for synchrony is ok, but the other two are html url links and have too many entries. They should be as simple as the synchrony one, and only one url.
-
6.3 has some significantly different structures to 5.8. webInterfaceManager doesn't exist any more, I think you'll need to try confluenceWebInterfaceManager
-
Yes, that's correct. The snippet I use as a base checks that a value is set if the issue type is bug: if (issue.issueTypeObject.name == 'Bug' & cfValues['DemoSelectList']?.value == 'Capital'){ throw new InvalidInputException("Something to tell a user what went wrong") return false } return true
-
Ok, the original question was edited, so the comments are out of context now. Use REST to get a list of issues and put them in a table in your code as required. See https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues
-
Yes, they need to be a JIRA or system admin, or be an admin for the board (that's separate from the project admin rights). JIRA admins can also change the owners of a board.
-
Same answer - you can only run it on one domain because there's only one base url. You are right in that you would need multiple servers if you want multiple url access to be done properly (rather than just a redirect to the right place)
-
It is slower, because it's doing all the hashing and user validation every time. Oauth enables the work to be done with internally cached credentials which does speed it up.
-
No, I don't mean his admin access. Is he a valid user in the project, one that can be assigned issues? His admin rights are about admin, not the project. Also, I remembered, despite being displayed as "andrew", does he have any uppercase characters in his ID?
-
Where is this velocity being rendered?
-
That log is all about LDAP, not a problem here. The usual thing with Synchrony is a proxy that's not set up to let it work. We'll almost certainly want to take a look at the config of that if you have one. Whether you have a proxy or not though, you should find there's a synchrony log in the same place you found the main…