Comments
-
Either remove the configuration that is trying to make it read the key, or put the key in the keystore with the right alias, the one Jira has been configured to ask for. I'm not sure I can go into much more detail than that - I don't know what documents have been read in order to try to configure this by your admins.
-
It's a wiki - a web service where people collaborate on the writing of, and share, information on whatever they want to talk about.
-
The logs you've shown us tell us that it is unable to load SSL Keys from the keystore because the ones you've pointed it to are not there. I'm not saying you personally has done something, but someone HAS misconfigured your SSL keystore. That is what the logs are saying, there is no other way to get this problem.
-
Sounds odd, the status of the version should have no effect on the ability to change the issue (unless you've implemented something to make it so)
-
All boards are based on filters. We need to know what the filter for the board is (unless it's a core/business board, in which case the filter is effectively "this project")
-
It looks to me like you have tried to give Jira an SSL key, but pointed it at a keystore that does not have a key in it.
-
Sorry, but "Web Gui stopped" is not an answer. What stopped, what does stopped mean? You'll need to read more of the logs - that's just part of it shutting down.
-
Usually apps (plugins/add-ons) are used, as Jira is built mostly for separate projects. Portfolio is one of the bigger apps for doing multi-project management.
-
I am afraid the answer is that you are probably going to have to read the logs. There's no way of knowing what the cause of the failure is, but the logs will tell you. I can't tell you what to search for in a log until I know what the cause is, and I can't know what the cause is until you've read the logs. I'd start with a…
-
You're going to struggle, even with log analysers - Jira uses REST calls internally, so you're going to find users issuing REST calls as part of their browsing.
-
You'll need to talk to the admins for the system to get your permission to move the issue granted, or the config changed to allow it correctly.
-
I would plan for a 6.1 to 6.4 upgrade as well, as 6.3 and below to 7 is not recommended. It can work ok, if your data is not complex (pretty much means "only a few simple add-ons"), but I'd allow for 6.1 to 6.4. On everything else, you're spot on. Copy the 6.1.1 to a test box, and do a complete test run through to 7.7 on…
-
You'll need to log into that system and close it there.
-
I'd use the ScriptRunner add-on with a "set custom field" script wrapped in "if <something>"
-
You'll need a little bit of code to provide it, but you can add a post-function that can check the commit and clear the field as appropriate.
-
Half of the Jira admin courses/training boils down to "use roles"
-
There's also a misuse of data in here. The estimates are for time effort, not duration. It's wrong to say "X will be delivered in 3 days time because the estimate is 3 days". And, in fact, your mathematics won't work. When you have a 6 day estimate, just adding it to (say) midday Tuesday will not give you a finish date of…
-
What do you mean "not about to search"? How are you getting and installing the add-on?
-
I asked for the errors, not for you to repeat what you've already said.
-
https://www.atlassian.com/partners/search?page=1 is a good bet
-
What are the errors you are seeing?
-
Do you have text or html emails set in your profile?
-
That looks like the standard outgoing mail. What is "broken" in it?
-
You will need to allow REST calls to all your users, or dashboards, gadgets and integrations will fail. However, your security requirements are based on faulty understanding. The REST API is simply a (slightly less functional) interface on to the web-ui. There is no point in blocking it because everything you can do with…
-
NO NO NO - Never put the resolution field on the edit screen. This breaks your system because issues become closed while open.
-
Create transitions from "closed" back to "closed" (or whatever your "end status" are), and give those transitions screens which include the resolution field.
-
Did you do this via the "find new add-ons" in the UPM, rather than an upload?
-
Your administrators have set the billable field mandatory, but not put it on the screens. You need to get your administrators to configure the field correctly - optional in projects where it's not on-screen or not wanted, and mandatory only in places where it should be.
-
* Set up your network so that the new urls land on the services. * Change the base urls in the "global configuration" for both services. * Regenerate any application links you have between them.
-
They're all still there, but in my opinion, a lot harder to work with. I'm afraid those of us who have signed up for Cloud have agreed to be lab-rats for new "experiences", it's in the wording. But go to admin -> labs and see if there's anything in there you can turn off.