When a person is the Assignee, that person becomes listed as the Closed By person when the ticket is closed, even if someone else actually closes it. How to fix this so a person's name shows up as closed by and not the assignee's name.
Ah, I see.....On "close" transition, i see the post-function as
"Copy Value From Other Field (JSU)
* Copy Field: Assignee to Closed By , overwrite"
How do I fix this? Should I just get rid of post function or edit?
From your description, I suspect you want to replace the post-function - I am not sure if you have a post-function available for this, but it sounds like what you want is "set assignee to %%current user%%". That will record the person who clicks "close"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a post-function for "update custom field" which is in one of the standard add-ons I usually use. I can't remember which one (hopefully JSU!). You enter the text %%current_user%% in the "what to set it to field". (Might also need to be upper case)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. I found it and added a post function and it is working now. But it looks like I broke something :( When I try to move the issue into one of the workflow steps I am getting an error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That looks like a script or add-on is trying to validate something that no longer exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you think I have removed two post-functions (see below) that are causing a problem? If so, how do I fix this?
1. The content of the field Closed By will be purged. (not sure how to add it again, any help will be appreciated).
2. Copy Value from Other Field (JSU)
* Copy Field: Assignee to Closed By, overwrite
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, removing post-functions will not add a function that looks for a custom field that does not exist!
Have a look at all the other post-functions and validators you have on that transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How have you implemented the "closed by" person functionality you are describing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't tell you. I don't know what you've done to do it.
At a total guess, it might be a custom field. Go to admin -> custom fields and have a look for it there. What type of field is it? This should get us started.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic for your help. I did check under custom fields and the field "Closed By" is showing up there. The type is User picker (single user).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so now you need to work out what is setting the field.
Again, a bit of a guess, but I would suspect the workflow - have a look at the "close" transition and check out the post-functions on it. My guess is that you'll find one that says "set custom field "closed by" to xxxxx"
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.