nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I add a new value on a closed issue?

Stefan Zabunov_3jirx5

Hello everyone!

I need to add a button to provide a new numeric value on a closed issue. It's not used in any prior screen or transition, so it's not an update.

I created the transition from CLOSED to CLOSED, created a screen, as well as a numeric custom field, but when I try to add the value, I see only "Summary" as an option.

Is it possible to even achieve this, considering the value did not exist in advance?

Accepted answers

All comments

Gökçe Gürsel {Appfire}

Hi @Stefan Zabunov ,

Could you share the transition screen configuration? Also, could you check your field configuration?

Regards,

Gökçe

said kouzibry

Yes it is possible to do this,

Even if a customfield did not exist before an issue has been resolved, its value can be added, either through a transition or by adding it to the edit screen, both would change the "updated" date on the issue.

The method you describe is correcte, however there are small things you may have missed, have you added your field to the screen you have created ? have you chosen the right screen as the transition screen ?

Stefan Zabunov_3jirx5

Hi @Gökçe Gürsel {Appfire} and thanks for your reply!

I apologize, I am not sure which part of the transition precisely you want me to share. Text, the diagram?.. I hope the attachment would be enough.

I have to admit that I tried to reproduce this based on a similar button we do have, but that one is used to update an existing value.

As for the custom field, I just added a new and selected "Number field" as this should be the expected format. I created a screen where I only have this custom field and later assigned the screen to the transition.

Thank you for your time!

Stefan Zabunov_3jirx5

Knowing it's possible is good, thanks for this! Now the question is what else did I miss...

Everything is completely new - the screen, the custom field, the transition.

Down to "having the button" I believe I made it - I see it only for issues in Closed status, as it should be. I just don't see anything but the option to leave a comment.

Stefan Zabunov_3jirx5

I believe I found the problem - it was the context. The workflow is used in multiple projects, but the context for the custom field I have set to only one of them. I updated this and I can see the value and also can update it!

The last thing that remained is how can I visualize this in the issue itself (somewhere under Details)?

Stefan Zabunov_3jirx5

I am sorry I posted this as an answer, just thought it would be easier since two people replied. @Gökçe Gürsel {Appfire} @said kouzibry

Gökçe Gürsel {Appfire}

Could you check the custom field context and see whether the project and the issue type are included?

Could also you check the Field Configuration that the project uses and see whether the field is hidden?

Best,

Gökçe

Gökçe Gürsel {Appfire}

No worries. I saw your answer when I posted mine. I'm glad that the issue has resolved

Have a nice day.

said kouzibry

I suspect two things you may have possibly missed,

Adding the custom field to the screen (since you only see the comment area)
- Go to issues -> Screens : In the search box, type te name of the screen you have created and click on it, then as shown below, in the "Select field..." drop down list,chose the customfield you want to show
As @Gökçe Gürsel {Appfire} has mentionned, check the field configuration, it's possible your field is marked as "Hidden"
- Go to issues -> field configurations, click on the field configuration corresponding to your project then search for your field, if you see the option "Show", then your field is hidden and you should click on Show to make it visible

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server