It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how to get rid of "issue.field.resolutiondate" in history??

what i did so far:

  1. uninstall Charting plugin
  2. rm -rf indexes/*
  3. rm -rf work/*

when jira is back online i still see issue.field.resolutiondate in the issues history.

how come this could be when this should be related to the Charting Plugin?

i really want to get rid of it cause this is kinda annoying

i already raised a support case back then in ${no_clue} and all i know atlassian created JRA-26274 from it...

any ideas please?


2 answers

1 accepted

1 vote
Answer accepted

It used to be part of the charting plugin but is now part of core jira.

Think you would need to override com.atlassian.jira.issue.customfields.CustomFieldType#getChangelogString to hide it, or the equivalent for system fields.

hmmm yes i've read about the switch from chart plugin to jira core...

can you please tell me what to do exactly to get it removed?

thanks in advance

yeah thats what i am goin to do...waiting. the JRA i posted was created in '11.

must be a bunch of bugs with high priority to get down fixing lower issues i guess.

thanks nic

You need to write some code.

Either something that removes the field from the core entirely, or just some tweaks in the field .vm to amend the history display so it simply doesn't show it. Whatever approach you take, it's hacking the core of Jira to surpress it. I'd be strongly tempted to ignore it until Atlassian fix it (which is more likely to be simply making the display nicer, rather than removing it)

I don't think this resolutiondate is related to that plugin. In the table JIRAISSUE you have this field as well so it seems to be a standard field like Created or Updated.

ok...some research resluts pointed on that plugin...

i saw it in that table before...i am wondering why this is not happening on one of my test instances...

From your screenshot, it seems that the resolution date change (old value and new value) in your Test instance do you have also issues where the resolution date changed?

How come the date changes if the issue never had a resolution date set?

I think the date is set everytime a Issue Resolved event is triggered

yes. on a new created issue the resolution event has never been triggered before.

but if i do resolve it i get this one..

we nailed it down to the database.

this won't show up if the database is Postgresql.

if it is mysql for some reason (atlassian is investigating) you will get this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Halp

Halp - Conversational Ticketing Help Desk for internal requests

From the Halp Team Howdy!  👋   We’re Halp, a conversational ticketing help desk for all of your internal requests in Slack (and soon to be MS Teams!). We’re excited to be a par...

57 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you