Database custom fields reset to default when editing issues

[Sebastian Westemeyer]

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

[Sebastian Westemeyer · Accepted solution]

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!

[Alexandru_Iacob]

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

[Sebastian Westemeyer]

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

Cheers,

Sebastian

[Sebastian Westemeyer]

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

[Sebastian Westemeyer]

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

[Alexandru_Iacob]

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