Database custom fields reset to default when editing issues

Hi!

In my Jira installation we use database custom fields to tag various workflow transitions with software version numbers from our database.

When issues are edited, all those fields are reset to their respective default values. This way our data is corrupted.

May this be a problem with ID_pk_VALUE mapping?

Regards,

Sebastian

6 answers

1 accepted

0 votes
Accepted answer

When I look closely I can see the drop down box displaying the correct value and then quickly switching to default.

This is a problem with Behaviour plugin. As soon as I disable it, everything works fine.

I will raise an issue with the Behaviour plugin.

Thanks for your support!

Hi Sebastian,

Can you please give us more details regarding your problem?

What version of DBCF and Jira are you using?

What is the exact configuration for the dbcf fields?

Are there any errors in the log?

Thanks,

Alex

Hi Alexandru!

Here are the parameters you requested:

Jira: 5.2.11

DBCF: 2.1.15

Katl-commons: 2.5.12

Select statement:

select VERSION, V.ID as pk
  from V_SPS_COMPONENT_VERSIONS V
  join SPS_BASELINES B ON V.BASELINE = B.ID
  join component c on c.ID = V.COMPONENT
where c.cname = {components}
   and B.NAME = {customfield_10014}
   and V.state in ('Stage_accepted', 'Released')
order by V1 DESC, V2 DESC, V3 DESC, V4 DESC, V5 DESC

Selected column is: VERSION

Type is drop-down box.

In this case there is no "none" allowed, so first item in list is chosen on editing issue, not the one already stored in customfieldvalue table.

If you need more details, just let me know.

Cheers,

Sebastian

Hi Alexandru!

Here are the parameters you requested:

Jira: 5.2.11

DBCF: 2.1.15

Katl-commons: 2.5.12

Select statement:

select VERSION, V.ID as pk
  from V_SPS_COMPONENT_VERSIONS V
  join SPS_BASELINES B ON V.BASELINE = B.ID
  join component c on c.ID = V.COMPONENT
where c.cname = {components}
   and B.NAME = {customfield_10014}
   and V.state in ('Stage_accepted', 'Released')
order by V1 DESC, V2 DESC, V3 DESC, V4 DESC, V5 DESC

Selected column is: VERSION

Type is drop-down box.

In this case there is no "none" allowed, so first item in list is chosen on editing issue, not the one already stored in customfieldvalue table.

If you need more details, just let me know.

Cheers,

Sebastian

BTW: this plugin is not open source, is it? Otherwise I would try and have a look myself.

Cheers,

Sebastian

No, the plugin is not open source.

You can enable logging with level debug and check the dbcf related messages from the log when entering edit issue; this might give you a clue on what's going wrong. Enabling log level DEBUG for kepler plugins is described here: http://confluence.kepler-rominfo.com/display/JJUPIN/Configure+JIRA+Logging.

I see you have a dynamic parameter in the query, that is customfield_10014. What type of customfield is it and does it remain constant?

If the problem persists, please raise an issue on http://bugs.kepler-rominfo.com/browse/DBCF, giving the details of the problem you are facing (screenshots of the problem would be really helpful).

Kind Regards,

Alex

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Marketplace Apps

Marketplace Spotlight: Zephyr

Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...

336 views 0 1
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you