Update propertyvalue of a workflow

Michele March 19, 2017

Hi,

I wanted to know how to update json string of a particular workflow using the "propertyvalue" column of "propertyentry" table of JIRA DB.

Thanks

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

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 19, 2017

I'm afraid that does not make a lot of sense.  Workflows are not json, and they don't have property values stored in the propertyentry table.

Could you explain what you're trying to do for your end users?

Michele March 19, 2017

Hi Nic,

I wanted to modify the coordinates of the statuses of a particular workflow using infromations stored into JIRA DB.

In particular I found PROPERTYENTRY table which contains md5(workflowname) using following SQL command:

select *
from PROPERTYENTRY pe
where pe.ENTITY_NAME='com.atlassian.jira.plugins.jira-workflow-designer' 
;

and related table named PROPERTYTEXT in which PROPERTYVALUE column should contain also the coordinates of workflow statuses (in json format).

If it is right, there is a way to change actual coordinates of workflow statuses modifying the content of PROPERTYVALUE column ?

Thanks so much

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 20, 2017

And this is another reason why I tell people not to read the database.

This is almost certainly the wrong way to approach every part of this, although there are still bits that do not make sense, I doubt they're going to change it.

  • What do you mean by "coordinates of the status"?
  • What do you think propertyentry data has to do with the workflow?
  • Most importantly, what are you actually trying to do for your end users?
Michele March 22, 2017

Hi Nic,

  • Coordinates: position of a status (Opened, Working, Resolved) into Workflow Design
  • Propertyentry: contains a column with workflow names (md5)
  • The workflows design has not been correctly migrated from JIRA 6.2.5 to JIRA 7.2.6. For this reason I thought to manually copying DB data from source to target JIRA version.

Thanks

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 22, 2017

I'm afraid that does not really help.

"Position of a status into workflow design" explains nothing.  A workflow is a collection of status with transitions to move from one to the other.  I don't understand what you mean by co-ordinates or position here.

Propertyentry does not contain a column with workflow names, it has some rows with that data in it for handling some stuff outside the workflow basic code.  I don't know why you are looking at that, as you don't know what it does.

The last point does make sense, but needs exploring.  You've taken workflows from 6.2 to 7.2, and they're not doing what you think they should.  But you have not explained how you have migrated them (upgraded a system? Native export/import?  Add-on export/import?), or what is actually wrong with them in the new system.  Has the list of status changed?  The transitions?  Something missing?

Michele March 23, 2017

Hi Nic,

I've migrated installed JIRA7 and then I've used backup file from JIRA6 to JIRA7.

The issue is that the workflow graphic representation has changed: the states are as you can view into the screenshot. The original representation, after data restore has been lost

Cattura.PNG

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 23, 2017

Right, so there's nothing wrong in the workflow itself, or any of the stuff you were looking at.

The only thing that has actually changed is the layout of the diagram.  These layouts are handled by code that has changed, so it is interpreting the workflow differently.

The only real fix for this is for you to re-layout the diagram, as the old code and new code read the data differently.

TAGS
AUG Leaders

Atlassian Community Events