Need to create a custom field in Readonly or Uneditable.

[Melina RAMPERSANDS]

Hi,

I want create a custom field in Read-only mode with default value as logged in user and the custom field must be Un-editable so the user cannot change the value.

Is it possible to create in JSM ??

[Paul Wiggers]

Hello @Melina RAMPERSANDS 

Yes this is possible. 

First, create a new, Read Only text field. Make sure it is available on the required screens.

Then, create an automation. In that automation you can edit the issue field and fill it with {{initiator.DisplayName}}

That should do the trick, please let me know if that works for you.

[Jack Brickey]

Ah yes...RO text field. Forgot all about that! 

@Melina RAMPERSANDS , rereading your post...I'm unsure of your intention with this field. Specifically, when do you want that field to be updated? Is it set once and remains static or does it change? If it changes when does that occur? The reason I'm confused, is you indicate the "logged in user". If you mean the reporter, then @Paul Wiggers automation is spot on. 

[Paul Wiggers]

@Jack Brickey I believe the initiator refers to the current logged-in user. Otherwise, you would need to use the {{reporter.displayName}} smart value.

But I agree, it would be nice to know a bit more about when the field needs to be filled so we can create a matching automation to help @Melina RAMPERSANDS out.

[Jack Brickey]

But isn't the current logged in user going to be the person reporting the issue? This is part of my confusion.

[Paul Wiggers]

Not necessarily, when we create an issue for the customer, we enter the customer's name as the reporter.

That means that I am the initiator, the customer is the reporter and my colleague can be the assignee. 

Let's us first wait on when @Melina RAMPERSANDS wants the field to be filled :) 

[Jack Brickey]

sorry, i should have said Creator as that was where my head was. agree...NMI

[Kimberly Blum]

Read-only fields are highly useful for a number of reasons, at any time. They can be used to create valuable reports. For instance, a read-only field populated via automation can be used to identify whether or not the ticket is billable. Since the criteria (e.g. project or issue type) may change over time, it's important to not rely on only filters and reports. Using a read-only field and automation means the criteria only has to be changed once - in the automation. Filters and reports continue to work with the new criteria, but the older information is preserved. Most important, the value is added automatically and is not changeable by the user.

[Jack Brickey]

Hi @Melina RAMPERSANDS , you can have the field on the Create and View screen schemes but not the Edit screen. Here is an article on managing screen schemes