Comments
-
The usual answer would be a pointer to the REST API docs. I find it's often more useful to start with the examples (with the rest of the docs available in the tree to the left) - https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/
-
One obvious question - why are you running stuff on the bash command line when you've installed it on Windows? None of the Unix environment will have been set up if you've used the Windows installation. It sounds to me like your windows installation has failed, and is unable to run, but you need to look at the logs to see…
-
Ok, you're on Cloud, which has a non-intuitive interface. Look for "settings" in the middle of the left-had bar under the "project" part. Like the admin cog in the good UI, it will only appear if you have admin rights.
-
There's an "administration" cog at the top-right of the screen, next to your profile icon
-
Where do you see this message? What do you see when you go to admin -> manage add-ons and look at the add-on?
-
No, because you run out of screen space on various devices
-
As Ann says, "Set JAVA_HOME on your Mac to a supported version." jdk-10 is not a supported version. See https://confluence.atlassian.com/doc/supported-platforms-207488198.html
-
When you are creating a new page, there are no watchers. There can't be because there is nothing to watch. So there's nothing to do here. If people are getting notified about new pages, it's because they have chosen to watch the space, and that means they choose to know about new pages
-
What does the marketplace entry say?
-
You do need them, as they're part of the issues that you have on the board. By excluding them, you're removing information that is part of the sprint, so the sprint can't work. There are many good reasons for hiding them of course. Even if there were not many, just "having a more simple overview of the board" is…
-
You are missing the point. You have to include the sub-tasks in the done column for the system to understand that they are done. To do that, they have to be on the board with a mapped status. Functionally, your board definition is incorrect because it is deselecting things you need on it.
-
No, I think I was unclear. Your "deferred" status does not matter how it is defined because it is not in the board's "done" column. The issues that are currently in that status do not count as "done" because they are not in the column. They could be outside the column for several reasons, the main two being because: *…
-
I am guessing what you mean is that you are expecting to find a custom field with a name that starts with "bom" where you have the highlight. The simple answer is that there is no such field there. There are a number of possibilities as to why. * You're looking in the wrong place (you are already by several lines, as "bom"…
-
Your issues need to be "done" in order to be seen as, well, "done". That means being in the right hand done column when it's a board. Closest I can get for you is Include the sub-task's "done" in the "done" column, so that they are done. Have a quick-filter for "issuetype in standardIssueTypes()" - when toggled, all your…
-
Yes, that's correct, you need to do it on a space-by-space basis. There are no other external user permissions - a person either has an account with access or they do not. If they do not, then their only access option is "anonymous"
-
Go to Admin -> Screens, find the ones that are broken (i.e. have resolution on them) and edit them. You need admin rights to do this though.
-
It did not delete the sprints because they are not project objects. They are created via boards (which are also not project objects) and handled outside both of those as separate entities in their own right. To delete the ones you don't want, create a new board and give it a filter that includes issues that were in the…
-
No. Anonymous users do not count towards your licence (because Confluence doesn't know who they are!) I would be very careful though - only allow them *read* access. A Confluence with anonymous write access available to the whole internet tends to last less than a week... To make it public, enable anonymous access in…
-
It's your server, set up by you, on your hardware, in your network. If it was not you who installed Jira on it, then you need to ask the people who did it for you. I know nothing about it.
-
At last. That means that Jira has tried to start, but has failed for some reason. Sometimes it might tell you a bit more under that error message, but often it is not enough. Your next step is to read the log file to find out what is failing. These are long and ugly, but should give you a technical error message near the…
-
When you fill in a resolution, Jira considers the issue to be "resolved", and hence strikes it out as needing no more attention. You need to remove the resolution field from the transition screen that is attached to "go to QA", so that you do not set a resolution inadvertently.
-
>Attlassian is not letting me log into my jira account. What error message do you get when you try?
-
They took a step forward a couple of versions back - 2 years ago, linking an issue fired no events. It now does fire events. But there's still no notification you can enable for those events. It does enable you to use code or scripting though. There are several apps that let you send custom emails when events happen. Now…
-
What. Is. The. Error. Message.
-
Please re-read the previous comment properly. Then tell us what the error is.
-
I'd point out that Confluene is a tool for collaboration, not being pretty. Personally, I'd like a little more control over the look and feel, but if I'm going down to css level, I'm probably going too far. When you have users who are confused and likely to make a mess that costs you time to fix for them, you have two…
-
This is not an error. "not letting me log in" is not an error, it's a generalised description of a failure to do something. Let's say I tell you "I can't drive to work today". Description is fine, but you ask me what the error is, repeating that is useless to you. You still do not know if it's because I broke my leg, lost…
-
From Admin -> Custom fields, create the field, then go back and look at its "context". You will find you can limit it by project and/or issue type.
-
There's not enough in that log to tell us what is wrong. What does the application log say?
-
Most things that are restricted in Cloud are restricted because Atlassian support do not have the time, money or will to support it when a user gets it wrong. A lot of the restrictions have been implemented based on the volume of support calls received that lead to lots of time chasing down configuration mistakes on…