Comments
-
To add to what Jack said, you should remember that the only thing that is migrating is your data. Your current hardware/server setup is irrelevant to Cloud. The method for moving both Jira and Confluence is "upgrade it to the latest possible version, then export it all to XML and import that on Cloud". We've found that…
-
It's hard to do it without a proxy, but the later versions of Tomcat may be able to help you See https://confluence.atlassian.com/jirakb/how-to-customize-customer-portal-url-in-jira-service-desk-server-847755218.html for the general idea. Just be careful to not redirect anything that isn't an issue key, and you'll need to…
-
Not with TFS2015 specifically, but I have done this several times. The only problem I've seen with it is ensuring the server is powerful enough to run both at the same time.
-
Yes, the installers will default to putting both in /opt. Generally, that's where I'd put them as well, although a lot of the time, I'll do something like /opt/atlassian-install/jira and /opt/atlassian-data/jira if I'm putting more than one Atlassian application on the server. The important thing is to make sure you don't…
-
Neither, it uses the "done" column on the far right hand side of the board.
-
Ok, so you've done the reconfiguration, are you still stuck somewhere?
-
No, because it puts too high a load on the server, and the output is utterly useless. As an admin, you should be questioning stupid "requirements" from your manager, and explaining that 30,000 issues in a pdf has no real world use. Ask him why he thinks he wants it, then explain why he's wrong.
-
Access is by tiers, not plain number of users. See https://www.atlassian.com/software/jira/pricing?tab=self-hosted
-
Those proxy paths are not going to work, because Service Desk lives within Jira, and you need to set the base url for the external source. So where you've got .../servicedesk/ that will be a base url and your service desk portals will be under .../servicedesk/customer/...etc... To redirect your service desk outside that,…
-
Remove the 8080 from your urls to check that the Jira is running behind the proxy ok first.
-
As already stated, the system is looking at the issue history to *calculate* most of those things, as they are not stored. Some sprint data can be found in table AO_60DB71_sprint, but you'll have to read the issue history (changeitem and changegroup) to calculate the rest.
-
It's the same answer - your report says "show me the labels", so it shows the labels on the issues that match "label = loc_*"
-
The layout you see in Stride is similar to the new design for Cloud services. It won't be going to Server before the next US summit from what I've heard.
-
I think you're missing a point here. You can not cluster Confluence Server, it will not work as anything other than a single node. You "normal drbd and pacemaker cluster" are pointless and can't be used with it. For clustering, you must use Confluence Data Centre. To use that, see…
-
See https://wiki.archlinux.org/index.php/systemd as an example. Most distributions document something similar.
-
There's no way Jira can know about your "manual process" unless you design it into your workflow somehow.
-
See https://confluence.atlassian.com/adminjiraserver071/translating-jira-802592307.html instead. There's no need to "create a dashboard and assign it", just change the system dashboard from the admin section.
-
Yes, it's in the "field configuration" for each issue type. You can change the "renderer" for the text fields.
-
It looks like you are on Cloud from the address you've given. This needs to be looked at by Atlassian Cloud support, as the investigation needs to look at the logs and networking on the server side. Raise it with https://support.atlassian.com/contact
-
There's no realistic way to do this. There's also no use for a pdf with 30,000 issues detailed in it, it's utterly useless in real life. No-one is going to read it. Could you explain what you are trying to achieve with this?
-
... and emojis by simple text, despite only knowing about four...
-
This is where I miss the "upvote comment" function ;-)
-
Hard to tell when the obscured bits might contain invalid characters. The login screen is mostly a cosmetic update to try to get Atlassian accounts in line with the way Atlassian want to do login (the mildly annoying and mostly pointless "ask for username first, then expand to password"). It does work though, you're going…
-
I don't expect this sample to be a lot of help, but yes, the double-quote = spam problem surfaced again (not while there were latency issues as far as I could tell). I snapshotted one that was a great example - with quotes, it was rejected three times. Without them around "events", it sailed through. ----- That is broadly…
-
Try removing the address line from your server.xml, you don't need it.
-
Assuming "hosted" means "Cloud", then the last login is in the user list section. You can't get to the logs.
-
Sorry, you've said "scrum" in the title and then talked about the Kanban board. I'm not sure which one you mean. I don't know what you mean by "horizontal line" either - could you screenshot it? Unless you mean "swimlane" or "grouping issues by their parent card" (what do you have under Board -> Config -> Swimlanes?)
-
Yes, back and forth transitions, but keep it very simple, having only one "held" type status. I'd stick with "On hold", and while I'd let people put it on hold from most status in the workflow, I'd generally only let it go back to early "to do" type status in the flow to show that more work needs to be done on it and the…
-
That is broadly correct. A listener picks up events, and the events in Jira (which are triggered by activity of varying sorts) contain a pile of information about what triggered it. They're independent of each other, so any given execution of a listener is based entirely on the data in its own event.
-
That is broadly correct. A listener picks up "events", and the events in Jira (which are triggered by activity of varying sorts) contain a pile of information about what triggered it. They're independent of each other, so any given execution of a listener is based entirely on the data in its own event.