Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Field Value Showing in View Screen But not Present in Edit Screen

J Manas Kumar
Contributor
March 28, 2020

HI I have Weird Scenario, i have A functionality that whenever i will remove a value from Story same value will remove from Epic from one Custom Field. That is happening, but problem is the value that has been removed is showing in View Screen but not present in Edit screen. This is Weird Case. Can anyone help me on this?

 

Regards

Manas

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 28, 2020

It is not very clear what you have set up or how, but looking at "not present in edit screen while showing in view" alone, there are two widely used way to do this

  1. The field is on the view screen but not the edit screen
  2. The field is read-only in some way - a scripted or derived field, or literally a "read only" type field
J Manas Kumar
Contributor
March 29, 2020

HI @Nic Brough -Adaptavist- 

The functionality is working as expected, i wrote one listener where if i remove a value from Story Custom Field it should delete or remove the same value from Epic Issue custom Field. 

I am not able to see the value in Edit screen that is correct only , because the value wont be present there, but its showing in View screen, i dont know why?

it should not show that , but still its showing.

I dont understand why?

Like we have Cache functionality in Java, Hibernate, is the same functionality is available here in jira? Is Jira storing Temporary Value?

 

 

Regards

Manas

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 18, 2020

Sorry for the slow response.

It sounds to me like your listener is not indexing the issue, so the new value only shows up in places where the database is read directly.

Suggest an answer

Log in or Sign up to answer