Comments
-
I suspect Confluence is using a version bundled inside some of it's internal add-ons, so the only way to know would be to read the code or un-bundle the add-ons and look for it. However, my Confluence does refer to it, and I suspect is therefore using 2.1.7 confluence# find . -type f | grep -i itext…
-
Yes, that was the next step, to confirm the certificates are valid. There's a utility called sslpoke which is really helpful because you can try remote urls with various certificates very quickly.
-
Good point, this is not a fault of Structure! I see it happen more often with larger add-ons (Portfolio, Structure, Script Runner, etc), and it's not the fault of the add-on.
-
On Server, there's a property you can set, but it's in a file - https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html However, you can't change those files on Cloud. I don't know if Atlassian support would set it for you, best bet is to simply ask - raise it with…
-
You'll need some code to do that. There's a couple of add-ons in the marketplace that provide it, and they're well worth a look - look for "update status of linked issues"
-
This is not a Jira or Confluence error in general, unless they've got something going wrong internally (which would have given you other symptoms). This is usually a problem when you have an external process making many, frequent calls to the services from the outside. Have a look at the apache access log - is it showing…
-
The board considers anything in the far right-hand column of the board to be "done". It does not look at status or resolution. You can use bulk edit to transition issues in the wrong status to the correct one en-masse, and I might be tempted to clean up the board by creating and ending a sprint. Next time someone wants a…
-
Go to "find new add-ons" and search for the Jira Toolkit, and install it. Then go to the list of custom fields, and click "add new field". In the selection, click "all" so you can search all the field types, and enter location into the search.
-
Due date should be in the list of custom fields once, as it's a custom field you added. There's only one time I can think that it won't be there, but you'd be missing other custom fields as well. I'd take another look! The permission scheme won't affect that list at all.
-
Shortly after Matt answered this question, Atlassian removed indexing options from Cloud, as they've tweaked it slightly and it's no longer needed for a Jira admin action (The changes a Jira admin might make that might trigger the need for an index are captured and trigger a background one in the projects affected) The doc…
-
Assuming Jira as you mention tickets. The short answer is no, as the notifications are sent when actions happen - that's what most users need from email notifications (although I think you'd struggle to find a Jira admin who doesn't think the default schemes are way too noisy). You can get subscriptions though - these run…
-
Ah, sorry, when people talk about boards, it's almost always Software ones. No, you can't configure the business boards.
-
That's odd, the system I've got (Confluence 6.4, Jira 7.4) works fine with special characters in the password. And username too.
-
Quick filters belong to boards, they're not the standard saved filters in plain Jira. You need to go to Board Config -> Quick filters.
-
For your title question - yes. Change the board filter to include more projects. For the body of your question - yes. An active user will use one of the "seats" of your 10 user licence. If you deactivate them, the seat becomes free for another person to use.
-
You absolutely don't want it to be mandatory! That would also break everything. You are right, it should not be listed in the field configuration at all, so no-one can remove it. There's an improvement request logged to get it taken off the field config stuff. Although we're all hoping that field configurations are thrown…
-
Yes, including removing them and adding your own quick filters. If "assigned to me" is not showing issues, then you don't have any on the board, or the quick filter is wrong. Check the board filter is selecting them, and what the quick filter definition is.
-
>also removed the resolution field Do not do that. There are vast amounts of places that Jira uses the resolution field, not just the system filters. You absolutely must have the resolution field available for all issues. If you don't want the users to set it, that's fine, you can remove it from screens, but you must set…
-
Indeed, it's not just broken javascript that does this, it's often just having the script there at all. You should not inject javascript into field descriptions in Jira, it's unreliable, doesn't upgrade well, and often breaks things.
-
Yes, I'm afraid you did waste a lot of time. If you were on server, there are add-ons that can help you transfer config, but Cloud doesn't support them. The best you could do is take a backup of Cloud, download it and restore it on a temporary server system, then use the add-ons to transfer the configuration to production.
-
REST respects the issue setup for the users, so you're not going to get anywhere unless you either stop sending due date and assignee, or you enable the users to set them in the UI. On point 1, where you could set them, it wasn't using the same user.
-
To see what is happening here, simplify. Jira has an annoyingly inconsistent approach to "something is done", but despite that, it is often easy to define when you know where to look. When you look at a Scrum board, it is simple. The issues in the far right hand column are "done", and the rest are not. The "green" or…
-
Nginx will work just as well as Apache, and is a bit easier to configure a lot of the time.
-
The usual culprit for this is that there's something wrong with the installation of the certificate that stops Java presenting something to Subversion that lets it get past the SSL handshake (note, it's usually NOT the certificate itself!) Sometimes, it's the key chain on the server not matching the certificate, but when…
-
Interesting, because it doesn't work that way on the installs I've got. But, I am definitely keeping this as a bookmark. More importantly, I want to say both "well done on finding it" and "glad you managed to fix it"!
-
I think your admins have made a mistake. The page properties macro does nothing like that!
-
Logs should be under <Jira home>/logs and <Jira install>/log. It's never been a good idea to run the Tomcat as root, no matter what the docs might suggest. "Run Tomcat as root" is bad advice. I personally always proxy it with Apache (because I'm familiar with Apache, having had some lessons from Dirk, Graham and Lars in my…
-
Exactly my thought too. Comments don't "go missing" unless bad things happen. It's far more likely that you can't see them in the UI and there's nothing to "import". (And no, "I am an admin" is irrelevant when it comes to it, admin means admin, not "I can arbitrarily see stuff that I might not want to as a user")
-
Mmm, good point - that doc used to be "this is how you do a cold standby" and then "and this is how you make it better with data centre", but it's now just a DC doc. There is no official doc, as it's not supported by Atlassian, but I know I've set it up loads of times for all the reasons you've asked. In most cases, it's…
-
There are no migration steps. As I've explained already, you need to look at what you did in the old system so you can carry it over to the new one. To do that, you need to understand what has been configured. The only way to learn that is to go through a process that tells you where to look - such as a fresh set up. I…