Comments
-
How are you trying to select the user? What does that do when you select one?
-
Ah, right, that's not a label, it's a version. Same applies though - you need to feed it a set of values that exist.
-
Oh, sorry, Semi and I were talking about the advanced search option. The simple search will give you an error because your label data is incomplete.
-
Ah, thanks Monique. That's a good summary of the guideline given there for us!
-
Spam is generally defined as unsolicited commercial email. When you post an advert on an old thread, it mails watchers. Including people who may no longer be interested, becasue the discussion has ended. That is spam. Necroposting is a post or comment made on a forum thread that is very old. This type of posting is often…
-
Ah, so Apache was serving up Plesk first on port 80 and then ignoring Confluence because it was listed lower?
-
Ah, ok. The upgrade process has removed your settings. I did a JIRA 7.4 upgrade the other day, and that at least had the decency to tell me it had trashed my server.xml, cacerts and setenv.sh files. From memory, older versions do it silently.
-
What version of JIRA are you using, and what is the error? I seem to remember that happening on a very old version of JIRA, but more recent ones tolerate non-existent labels, they just ignore them like Semi says.
-
As you wander through projects with different field settings, you kind of accumulate them.
-
That implies the url you have followed is broken. It's hard to tell without seeing it, or knowing what you're doing. The log might be worth reading as well.
-
I'm not sure I can expand on "search for issues you want on the board, save the filter, go to create board and answer the question it asks about what issues you want to use by selecting the filter you saved"
-
Save a filter for "project in (list of projects)" and create a board, selecting your saved filter as the source.
-
Ok, well, we need to look at what the server is doing, but on Cloud, it's a mangaged service, and you don't have access at that level. You should raise it with https://support.atlassian.com/contact - they can look into logs etc for you.
-
Hmm. The only thing I can think of is that there's a problem with one of the deactivated users that is making it think they are active. Can you check that none of the deactivated users are in any administration groups? And then activate and re-deactivate each one?
-
We will need to see more of the errors. It's looking for something with an invalid file name or something that is not there, but we can't see what from only part of the error
-
It's the physical server logs you need to see. <jira home> is the directory JIRA keeps its data in on the disk. That question makes me think you might be on Cloud, rather than Server, is that the case?
-
They look like spam to me. Adverts posted, irrelevant or wrong, on old threads (necroposting).
-
I suspect you might be able to parse the .vm file for the User Picker as it's built into JIRA, but you'll have to do it with the right context set, providing all the variables it needs in it. Might be easier to use it as a base for your own coding.
-
Could you show us the user list?
-
Not quite what I said. The easiest thing to do is take your jira-software-users group and grant it JIRA access on the Service Desk server. Not Customer access, but proper full JIRA access.
-
I don't know, I think you'd want to read the api for the exact calls it may be making.
-
No, that's not possible.
-
Are you able to take a business project and change it to a Service Desk one?
-
On Cloud, you'll get the option to "log in as" a customer if you are an admin.
-
There's a swathe of things this might be, but let's get the easy one first. Get Michel and Ryan to go to create an issue and click "configure fields" at the top right of the popup - are the fields de-selected in there?
-
The Customer is not getting an email because of what I said before - the assigning of an issue is a JIRA activity, not a Customer facing event, so they won't get an email about it. I suspect the technician doesn't get an email because they have "do not email me when I make changes" set in their profile (it defaults to not…
-
Well, that was easy - your connection is using the wrong user/password to log into the LDAP server.
-
Start in <jira home>/logs and with the atlassian-jira.log file. There are others we might look at, but that's the starting place. If you're not sure of <jira home>, then Admin -> System info will name the log with the full path.
-
Is there more of your log? My guess is that your server update broke either a path or added some security checking that breaks it, but it's impossible to tell from that snippet of log.
-
What do the server logs say?