I have jira installed on my server.
It was running at http://[my ip address]:8100. I could manage to change it to http://jira.[my domain].com.
Now after I access it at http://jira.[my domain].com, a browser path changes to http://jira.[my domain].com:8100/secure/Dashboard.jspa.
Why does the port show up?
Is there any way to remove 8100 port from this redirect.
I would like Jira and Github to talk to each other so commit messages with ticket names show up in the ticket. Issue sync would be nice as well.
I know jira has a DVCS connector but the documentation is piss poor. From what I can tell that and the Github hooks require our private jira instance to be available from the public internet or at least github's servers.
I'm developing web application using Spring roo (mvc), this application is the ERP system. I plan to use Jira as my issues reporting system. My question is, if is there any solution that will help me report exceptions thrown in my web application in jira automaticly?
I thought about creating some script that will be scanning logs and creating issues in jira. What do you think about it?
I have Jira installed as a service on my Ubuntu VPS on 8080. I've successfully used ProxyPass and ProxyPassReverse to point http://jira.mydomain.com to http://mydomain.com:8080
However, after login, the URL in the browser is changed to http://mydomain.com:8080/Dashboard....
I have a server running Jira and Confluence.
Jira @ http://jira.domain.com:8080
Confluence @ http://wiki.domain.com:8090
I can reach the applications from the server, from my home pc. But on my work pc only Jira is accessible.
I'm trying to get the certificates just right for our Jira/Confluence deployments in house. People access them differently, either from the hostname or the fqdn. I'm using java 7's keytool so I have access to the server alternate name functionality:
-ext san=dns:jira
and I hand it
jira.example.com
as the CN when generating the certificate.
I connect to server with PuTTY from Windows.
I have a long yet not touched (I suppose) by hands of local admin config:
$ cat /opt/jira/.subversion/config
...
I'm using Jira on demand and I'm trying to change the default groups a new registered user belongs to.
A soft limit of 200,000 issues has been lifted thanks to performance improvements in Atlassian's JIRA 5.1. The update also includes inline editing support and customer issue collection support...
A soft limit of 200,000 issues has been lifted thanks to performance improvements in Atlassian's JIRA 5.1.
Email this page
