Comments
-
There is a multi-level-cascading-select, but it does not work in Service Desk. Your Agents will be able to use it on the issues, but the customers will not see it on the requests.
-
The email is being used as a unique identifier, so that people can have multiple accounts.
-
Either you are not an admin, or this is a project created by an individual user for their own use (these can't be configured a lot, they always use simplified workflows, fixed fields etc)
-
The .net call is being made to a server the machine cannot locate. That's either you giving it the wrong name, your network not knowing how to resolve the name to an address, or your network blocking the route to it (although that third one should usually give a different error message) Try an nslookup on the name of the…
-
I think you need to give us a little more context. Whih StreamAPI are you using in Confluence? How have you added it? In your .Net application, what are you sending to Confluence?
-
Sorry, I should have emphasised this better in the first answer. Yes, by creating a new "workflow scheme" and applying that to the project
-
That was a bit of a flippant answer on my part, I hope you didn't find it too annoying! I think it's worth expanding on though. The initial thought was born of my brain going "if it costs you $50k to enable a standard, well understood, globally used function that takes 2 minutes to enable, then your mail server is probably…
-
Could you explain what you are not clear on, when you read https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html ? It's not the clearest of docs, in my opinion, but it would be good to know which bits you are struggling with?
-
What type of issues are not burning down?
-
@Alessandro Tondo- I'm afraid you've misunderstood that. The new look and feel mentioned in 7.10 is a change of colours, icons, branding and so-on. The discussion here is about the new UI layout found on Cloud. Which is a matter of contention (Cloud is very much losing customers because of it, and even some of us fan-boys…
-
I thought they were tagged with "atlassian support" already? Or is that a tag from a different source?
-
The status categories in Jira are hard-coded. They are held in a config file, but even if you added "pending" to that, it would not do anything (other than show in a couple of places) without you re-writing swathes of code within the core of Jira. Generally though, "pending" is usually a "to-do" status - it fits the…
-
No, it's not. Jira Software sticks to the full scrum committment and definition of done - either an item you committed to is done, or it is not. There is no partially done, it's a binary flag. You only burn-down on items that are done. There are plenty of good reasons to be able to see progress, but they're not burn-down…
-
You can go straight to 6.9, but before doing so, I would read all the relese notes for each version (6.1, 6.2, etc) to identify areas of change that affect you, and, of course, do a test run first!
-
You should get in touch with support, but I would look at the application log file first, it should contain something with a bit more information about the underlying error.
-
The Apps don't know where they might have been configured (and also don't want to destroy your config if you remove them and might want to put them back), so when you run into this, it causes problems as Jira tries to load classes that aren't there any more. The easy(ish) fix: * Get the list of errors as you have above *…
-
Yet another reason why reporting on Jira with SQL is a poor thing to do. The answer here depends on your database flavour though, not Jira. There should be some function in your database that outputs dates as a human date time.
-
Once a workflow is "simplified", it is locked down, as most changes aren't allowed. You de-simplify by creating a new "workflow scheme" and applying that to the project.
-
Hmm, sorry. How about cat /proc/meminfo
-
Please try cat /proc/memstat on the box, and give us the first three lines? (Or MemTotal at least)
-
And the memstat output?
-
I was simplifying, I know there's more mistakes than just "everything on the left", but I wanted to be clear it was that change, and not the lesser issue-view changes
-
Absolutely, just leaving the port in place is a really simple approach, and there's nothing wrong with it. Getting rid of the port is something humans like doing, but in reality, running on port 80 just means "Browser: please assume no port = 80 for http". Yes, for http://jira-uat.dx.local:8080 you need context = "", and…
-
The database is located whereever you told Jira to look. If you used the internal database, then it's actually a file in the home directory under /database and you'll need extra database tools to read/edit it. The database type will be h2 (assuming you're using Jira 7)
-
It's more the case that Symantec Antivirus does not really support Java properly, and tends to harm the execution of such programs quite badly. But yes, you should get rid of it if you're going to run Jira. There are some others with better Java support, but even if you do go for them, you should exclude Jira from the…
-
I am afraid the only way to go back from "everything on the left" is to migrate off Cloud and on to Server, where it hopefully won't arrive at least until all the problems are sorted out.
-
It's definitely not malicious, there is a vulnerability. The team has concentrated on fixing, patching and getting updates out to people who may be affected. I'm expecting a wider announcement and some more detail soon.
-
The base url in Jira is used internally by the application for internal linking, putting on emails, connecting to remote and local systems and so-on. Jira runs on Tomcat, which can relocate systems it runs on different "contexts" if you need to run more than one, or want them to run as part of another site. Imagine a…
-
Start at https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html
-
Ok, then you mean "no", as it does not share authentication with Jira. You can do this without SSO, but your other system is going to have to do some work. First, working from the email address, ask your directories what the user's Jira account is called, then, second, establish an Oauth connection with Jira so that the…