Comments
-
You'll need to explain what this has to do with Confluence in more detail.
-
You can remove it, but you must replace it with groups covering everyone who needs to be able to log in (i.e Employee and External) As a system admin, you should be able to do this. You will need to add the replacement groups to the permission before removing the confluence-users from it.
-
The internal database is not suitable for production use - it can fail catastrophically without warning. You should use one of the supported external databases for production.
-
Gitlab does require a database, but it just uses an internal one without asking. Bitbucket lets you choose between external databases so that Atlassian are not re-inventing a wheel and allow you to use the one best supported by your organisation (often avoids having to worry about backups etc)
-
You can drop add-ons into the plugins directory and restart Confluence, but there are some add-ons that don't work if you do it that way. I would strongly recommend not doing this though, you should use the API to install add-ons (via the GUI)
-
You are getting errors which are quite vague in what they are saying and could be caused by all sorts of things. Including an unsupported database. It's utterly irrelevant how it has been working. You now have an issue with it, and there is no way to rule out "your database is broken", until you start running it on a…
-
I understand "move it to a drop-down when there are too many", but the good thing about quick filters were that they were quick. It's in the name. You're right. The drop-down doesn't work. It needs to be something like "your first 7-ish filters are buttons across the top, but when you create too many, then we'll shove them…
-
Mariadb is not supported, what happens if you try setting it up with a supported database?
-
That thread is well worth a read for anyone thinking of using Cloud. And anyone planning to be using Atlassian long-term. The new UI will eventually make its way to server as well, and, unless Atlassian start to do something useful about the problems reported there, we'll all get lumped with a functionally useless…
-
Bother, that makes it a bit harder to diagnose, but it's good information. So, your Jira is not starting. Could you tell us what you get when you visit the url it should be running on in your browser? Also, can you read back through your log file? This is a pain for most humans, but we need to be a bit clever - we need to…
-
:-) When they gave the internet to her, or when they realised they forget to get it back, several years later?
-
I usually do the label/properties for the more structured and complex templates, not the every-day ones. In other words, nothing I usually write - I've been trained to keep it simple and accessible, with human language. Templates for me just save me a few clicks to do something regularly (I usually stick to a template with…
-
I think we may be talking too fast - those still look like catalina.out errors. Is that right? Or are they in atlassian-jira.log?
-
I have it on my to-do list, but never seem to find time. Always too busy trying to make sure Jen doesn't drop the internet again.
-
Ok, that's vague (Tomcat's fault, not yours). Could you have a look at the application log - <jira home>/logs/atlassian-jira.log by default.
-
No. The templates are point-in-time, they run "now" and don't get referenced again. Once created, a page could easily be changed beyond all recognition of the template, and the creation template really doesn't matter after its first use. You could amend your templates to have a label on them, or even page properties (your…
-
What does the log say the problem is with restarting?
-
The issues template sounds like a good fit here, but I'd also look at "canned responses". The add-ons doing that a bit more focussed on helldesk work, rather than Jira in general, but can do some excellent one-click work! (Not that I would ever think of Roy Trenneman's tape-recorder here...)
-
Both of those choices are excellent for exactly this. I work with the Echlin, so I'm a lot more familiar with ScriptRunner. I have a very strong feeling that Automation can do this too, but I have not tried it, so I can't be sure. With SR, I would * create a custom field (probably a multi-check-box with only a single…
-
Service Desk and Software are "applications" that are installed on top of Jira Core. If you have no Jira install, then using a .exe file to get started is the right thing. If you already have Jira running, forget downloads, go to Admin -> Manage applications, and install from there.
-
Yes, check the space permissions and make sure "anonymous" has no rights other than "read". If you think you've done that, then we're going to need to see the permissions for a space where you think anonymous users can post.
-
You will need some form of automation (not off-the-shelf) to do this in one step, but it's certainly possible without add-ons in two. Imagine a basic scenario (mostly to help me "think out loud") * User rings agent, and asks for an easy thing * Agent starts to create issue to log the call, leaving it open while on the call…
-
There is no "system" field built in, so the table you need is customfieldvalue, which you're going to have to make all sorts of horrid joins with to make any sense of the content. Please, don't use SQL with Jira's data store. Use the API.
-
Can you go directly to the issue view of an issue you know exists? e.g. https://yourjira.com/browse/ABC-123
-
In what context?
-
Make the field optional in the field configuration, or remove it from the context for the project (the second one will destroy any data in issues the field was on)
-
No. The REST API uses "fields=" as you saw earlier to filter down what fields it sends back for each issue. The reason we've suggested Script Runner is because you want status IDs rather than status objects, and it might be quicker and easier for you to get groups of issues, rather than a flat list. The built in REST API…
-
No, they've chosen not to get notified on their own changes, so the mails will not go out.
-
You might want to explain the difference between "JSD Portal login" and "Customer Portal Login", as it sounds like they are the same thing to me (might be just the way I'm reading it)
-
Not quite, it's neither of those approaches. ScriptRunner is an add-on that works within the core of Jira. One of its functions is to provide REST end points. You write code that uses the internal Java API to get the data you need when something pokes that REST endpoint. Your code is dependent on Jira and ScriptRunner…