Comments
-
Use the same words, but put extra spaces in them if you have more than one word in a name. Or add punctuation
-
I'm guessing you have not managed to find the documentation as you're asking this. Check the descriptions of the available calls in https://docs.atlassian.com/jira/REST/server/#api/2/reindex
-
Those are not fatal stop-dead errors. You'll need to find the errors that tell you what is stopping JIRA completely. Check more of the log you've read for severe errors and have a look at the "catalina.out" log too.
-
In memory, as there's no use for the request id's outside the running process.
-
Both of those look correct, although you should use one or the other (if you use both, the users will select a resolution and have it overwritten by the post function) But we need to be clear on what is "not working". Can you try transitioning an issue through the transition you have added them to, and check the resolution…
-
There are only two things I can think of here: 1. You have removed the "done" resolution after setting it up in the post-function. However I would expect that to show errors in your screenshot, and not allow the transition to proceed. 2. You are not actually using that transition. You might be accidentally selecting one…
-
> it kept failing to create a number of files so I skipped them It sounds like you have got the wrong permissions on the installation, so the update can't change all the files it needs to
-
It's the number of users - starter licences are for 10 users. For support, you need the next tier up.
-
Yes, it's annoying (especially as turning off the edit just disables access to the UI, like it should do!)
-
Yes, it's gone away in recent version of Cloud.
-
Sorry, I really should not trust my memory. jira.permission.comment.denied for the key, and leave the value empty.
-
There is no "watchers" custom field in JIRA. People usually have it because they have installed a "watchers field" add-on. Install one of those and try it again.
-
Which columns are these issues in on the board?
-
Ahh, sorry, I didn't see the "starter" in there. You can't raise support calls for starters.
-
From memory, jira.permission.comment for the key and denied for the value.
-
You can't quite do this, for several reasons. Boards are not project aretfacts, they are not "in projects", they're independent entities, which may include several boards. Also, a board is not a container for issues. It selects them from the projects behind it. So, to "copy the information", technically, all you need to do…
-
Your second screenshot is for raising the support request. (Even if you get someone on the phone, they won't engage with you on a support call until you've raised a request there)
-
Did you install or upgrade an add-on? Could someone have downgraded your rights? Are you on Cloud?
-
You could re-use the priority field, but that affects all your projects, with a shared list of priorities which probably won't work for everyone. I would add a custom field for it with an indicative name like "Request priority". You'll be able to filter on a custom field quite easily. I'd strongly recommend a single-select…
-
Could you explain where you are trying to terminate the SSL connection? In other words, is IIS supposed to be doing all the SSL work, or are you trying to make JIRA's Tomcat do it as well?
-
Could you tell us what version of Confluence it is, and what it is reporting for its java version?
-
Those three levels would normally be represented by a priority or severity type field, not as request types. A request is supposed to be something where a user asks for something. You usually ask your IT people for "fix the printer", "reset my password", "I need a new laptop", not for "high", "medium" or "low". Those are…
-
Hmm, those look ok to me. We could go into that a lot more, but it may be a red-herring too. Could you look at the log file again and look for the errors that occur when you are clicking "next" on the licence screen?
-
That looks like you have set it up successfully, then tried to connect an external user directory, but that connection is failing? Is that right, you've got through the setup ok?
-
I'd expect a lot more than that, and something mentioning licencing. However that error is a "Garbage Collection" error, and that could well be the system failing at the wrong time, or triggered by memory changes as you try to apply the licence. I'd want to fix that in any case. What are the memory settings for the…
-
That's exactly the right section. Mine is a little different in structure and says ProxyRequests Off ProxyPreserveHost On <Proxy *> Require all granted </Proxy> ProxyPass /jira http://192.168.1.144:8081/jira ProxyPassReverse /jira http://192.168.1.144:8081/jira But I think your structure is an alternative way of saying the…
-
Its in <jira home>/logs by default. I'd expect atlassian-jira.log to be the one the error goes into.
-
Yeah, that confuses a lot of people - there's "Apache" the web-server, and "Tomcat", which is technically "Apache Tomcat", the application server. Tomcat doesn't do proxying itself, not without a proxying application added to it (which you generally wouldn't do). Most of us run Jira on a Tomcat located behind a web-server…
-
Does that error happen when you click "Next", or is it there when you get to the screen? What does the log file say when you trigger the error?
-
Bother scheme="https" proxyName="jira.jirahost.com" proxyPort="443" secure="true" Is the bit I was looking for and it looks fine. Next question is what the proxy is set up to do - nginx, Apache or something else?