Comments
-
That's not "depth", that's "a number of versions". There is no limit - the point of a wiki is to keep them all!
-
You will need to set up a standard authentication system that can draw from your database (or you can import your data into, so you can throw it away). Or write an authentication system that can use your data properly.
-
You can change the board filter so that it orders by priority instead of rank. But be aware that this makes the ranking useless, because to order by a field, you have to, well, order by it.
-
Yes, it will work. The transitions do not have the same ids (they physically can't they're unique), so I suspect you are looking at something else. However, to get your exact aim, you are going to have to remove the "all" transitions - they really do mean "from anywhere" and you need more control. So, what I would do is…
-
For standard projects, there's a good write up at https://community.atlassian.com/t5/Jira-questions/JIRA-Software-project-permission-restrict-user-access-to-one/qaq-p/779572
-
Could you explain what "versioning depth" is expected to do? Confluence pages are simply versioned for each change made to their content, so I suspect you won't get what you want, but I can't be sure without knowing what that is!
-
Jira 6.1.5 Server is a Jira Core, even if you've got Software and/or Service Desk running on top of it was well. To from one server to another, set up a new 6.1.5 Server Core install and export and import the data (or, you can be lazy and just copy it!) I suspect there's actually a different question here, like you're…
-
The email alerts should be telling you who deleted the comments. Could you check that?
-
Once you've identified the version you want to look at from the list, you'll need to ask it about its release status. getStatusObject is about issue status usually, versions don't have a status. You'll want to check isArchived and isReleased (if neither is true, it's an active version)
-
We'll need to know what Confluence you are running (the Server version, or if it's Cloud) and what App you're trying to install. This error happens most when you try to import a Connect App into Server though, so I'm guessing that may be what you've tried.
-
No, it doesn't have calculated fields off-the-shelf (barring some hard-coded ones like the work progress etc)
-
User macros are very different to macros from Apps - you'd probably be able to work out the logic, but translating that into a Connect Apps is pretty much a rewrite!
-
You can, but it's raw XML so you'll have to parse it after extracting it.
-
You can set this by setting the opsbar-sequence property on the transitions. See https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html
-
Actually, as a project admin, you can not select a new notification scheme. You need to be a Jira administrator or above.
-
Confluence is the better place for a knowledge base - it's designed for us to write, collaborate on, and share docs as easily as possible, whereas Jira is an issue tracker, so it's aimed at more structured (field based) data and having a workflow that eventually says "this issue is done, so it will generally be ignored…
-
Roadmaps only exist for Cloud Jira, and we don't have a timetable for them to make it to Server.
-
You could validate instead - on a transition, use a validator that checks what you need and refuses to let the issue move on unless it is correct.
-
Ok, I can't see anything that would be doing this, unless you're not logging in as the user or a member of the group that is named in the "browse" permission (it looks like you are explicitly naming yourself) So the other thing is to look at the issue security - is there an issue security scheme in place on the project?
-
They look like they should be add-able, as they've got "use" on the space. All I can think of is that they're not really confluence admins, just site.
-
?Have you checked that the field configurations for the text fields are set to use the rich editor and not plain text?
-
Yes, that's because a full lock and index rebuilds the index files you destroyed.
-
Yes, it's because there's several strategies people might use, and Atlassian have dodged the question of which one to implement by not doing it at all.
-
Cloud, no, Server and Data Centre, yes.
-
Again, the property belongs to the status, not the issue. There isn't anything to override based on fields, because it's a status property.
-
That could be a number of things, but usually means the Tomcat is running but unable to serve up the application. Clear your browser's history in case the problem is based in your browser, but if that does not help, you'll have to read the server logs to see what the problem is on the server side.
-
The articles I pointed to before are about moving a Jira and Confluence to a new server. I suspect you've missed the parts about relocating the databases (assuming you need to move them)
-
This error does not look like a Confluence error - could you tell us exactly where this error happens and what you're doing to provoke it?
-
If you are on Server, then you'll need to read the logs to find out what the error is. If you are on Cloud, you'll need Atlassian to read the logs - raise it with them at https://support.atlassian.com/contact
-
Not built into Jira - you'd need to re-write the menuing system.