On Jira, I have a field called re-opened count which in essence every time the bug is re-opened the count increments however I've noticed this only works if it doesn't have a count present once we hit the count of of 1 this no longer works. Any ideas why this is?
The code is as follows: -
{{#=}}{{customfield_10401}} + 1{{/}}
Jira restart and server restart did not help
This should have allowed you to get back into your Jira.
If there are no errors, then you can do a:
curl -LO http://127.0.0.1:8080/jira
to check if its really up or not.
Hi, did it!
in browser still 404 error.
from atlassian-jira-security.log:
2018-06-21 09:17:42,426 JIRA-Bootstrap JIRA 7.10.1 build: 710002 started. You can now access JIRA through your web browser.
and from atlassian-jira.log
2018-06-21 09:18:57,794 HealthCheck:thread-4 ERROR [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to 217.74.43.163:443 [/217.74.43.163] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After some tomcat tuning it successufully started and its work!
But still couldnot get access to dashboards: /jira/secure/Dashboard.jspa
217.74.47.6,127.0.0.1 /secure/Dashboard.jspa [c.a.g.r.internal.http.HttpClientFetcher] Unable to perform a request to: https://217.74.43.163/jira/rest/gadgets/1.0/g/messagebundle/und/gadget.common%2Cgadget.issuetable%2Cgadget.assignedtome%2Cgadget.issuetable.common
org.apache.http.conn.ConnectTimeoutException: Connect to 217.74.43.163:443 [/217.74.43.163] failed: Connection timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:157)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
and this question also solved: by default datahoster did not provide the access from local host to public interface
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.