Comments
-
$10 a month is horribly cheap for a Cloud service with everything Atlassian offers for it. If it is too much for you, then move to "server" - download that, pay $10 for a year rather than a month, and absorb the cost of install/admin/maintenance for yourself.
-
Stop Confluence, use the database tools to change the name, edit the confluence connection settings in <confluence home>/confluence.cfg.xml to change the database name it connects to, and restart confluence.
-
There are some things that probably should not be shared. Maybe when you're in a safe space, with your counsellor / psychiatrist / partner-who-REALLY-loves-you-despite-everything / etc. Thank you for providing a safe space by setting a context that makes it ok to admit to this. I'll keep the answer short, and skip the…
-
You don't. There is no longer an option to go back, If it's causing you too much frustration, you have the option of migrating to Server to get the "old" UI - that is not going away for a long time.
-
On the "breaking existing stuff" - you're fine. The regex is only used to stop you creating projects with dodgy keys, you won't have any problem with existing projects or new ones that still match the old pattern.
-
Have a look at the raw number that your subtraction gives you - your scripted field is converting it to text based on the wrong unit of measure.
-
There is no "restrict". To stop someone seeing a project, remove their access to it. Look at the "browse project" line in the project's permission scheme to see how they get access, and then make sure the user does not match any of the rules.
-
Projects don't have an update date, so can you tell us what you're planning to use instead?
-
I'd guess that is text wrapped in a {panel} macro
-
I'm not great with regex, but I think it's a bit more simple [A-Z][A-Z0-9]+ will work fine [A-Z][A-Z0-9_]+ will allow underscores and break some things (Mostly Apps to be fair - you won't have any problems in Jira)
-
The pattern is regulated by a regular expression in Admin -> General -> Advanced. But don't change it - there are some "interesting" things (i.e. stuff breaks) that happen when a project key is not the standard. Stick with A-Z as the first character and then A-Z,0-9 for the next 1 to 9.
-
It's the first column in all three tables of types of access (Group, user and anonymous).
-
That's odd, mine auto-filters fine. But I notice that "designers 2" is not in the "users" panel where you're looking at assignee, which suggests it's not a user-picker?
-
Use Issue level security
-
If you've temporarily accepted all third-party cookies and still can't log in, then it's not the cookies causing the problem (although to try to answer the question, I can log in fine as long as I accept cookies from *.atlassian.com and *.atlassian.net) I've also got fingerprinting resisted and have no problem there…
-
My best guess is that it is a problem when the database is being hit rapidly and repeatedly in order to do something like an export or backup. You'll need to work through the doc I linked to earlier to try to find out if this is the case and what to do about it.
-
Do you have the "global" permission for "browse users"?
-
The spam filters make mistakes, although in this case, I can't really see anything in the post that's one of the usual triggers (lots of code or logs or links) and your research is spot-on. I've un-spammed it now.
-
The administrators of the PEC project or the administrators of the system!
-
Yes, on the classic boards.
-
There's nothing in Confluence that would switch the backups on - the only way to do it is with a new installation or by an admin enabling it.
-
Oh, that's the other user's screen! Sorry, I thought it was yours. When you type in "pec" you don't get the project she finds. Not issue type. That means you don't have "create issue" permission in that project.
-
I hope they are - I helped write a load of them over 3 years ago, and we were trained to write questions that were clear and understandable, with selections that were inarguably right or wrong. There was a rigourous peer-review and atlassian-review process and extensive beta testing weeding out and improving or discarding…
-
See the discussion above.
-
Um, the payload is your data.
-
As long as the version of Java in use remains supported, you're fine with this move. Doesn't matter which way round you do it.
-
https://library.adaptavist.com/entity/update-the-value-of-a-custom-field-using-a-listener has some listener code that lets you read through what is contained in an event (including field changes)
-
View and edit have been separate permissions since Confluence version 1! The way restrictions cascade down has changed a bit, but not space view/edit
-
Go to "configure board" and then "columns" (this assumes you are a board admin, and that the board is a Classic Software one. If it's not, then the columns follow the workflow)
-
Again, it's not my email. You need to talk to the administrators of your system. We are not your admins, we are users of related systems that you may or may not own.