How can I leverage Comala to build an approval workflow for Release & Deployment plan in Wiki?

[starryeyes]

I am trying to streamline my team's release & deployment plans. Major issues found:

- Tracking required sign-offs to approve release and deployment plan

- Sending escalation when approval is not received by specific parties

- Restricting editing during certain approval phases

- Allowing editing for specific users at specified phases (i.e. Operations team can upload documents and change request tickets at the Ops Review phase)

- Reusing the approval template for new R&D plans without creating a new workflow

At the moment, my team currently tracks approvals via email. We would want to move away from using email as form of tracking approvals on release and deployment plan. Our release and deployment is maintained on the team's Wiki Confluence site. However, we are trying to find ways to 

(1) Identify data that needs to be provided at specified time (i.e. Draft phase the following fields are required prior to submission)

(2) Identify users that must supply specific information at specified phase (i.e. If specific group has a release, the leads must enter data in specific fields)

(3) Restrict users from editing during specific phases (i..e. Prod Ops can only enter data during Prod Review which does not return the content to draft)

(4) System send escalation to specified persons when approval is not received at a specific timeframe (i.e. PM fails to provide feedback an email is sent to senior management)

Confluence has Comala workflow as an existing plug-in feature. I tried testing out this feature but I noticed there some limitations using the workflow builder. Does anyone know whether Confluence/Comala can be leverage to build a robust in-house application described above?

[Falk Eckert]

Hello,

i found the reason of the nullpointer: i clone an issue with custom-field in another project. In this target project the custum-fields ar not defined.

Question: how can i define custom-fields for this target-projet in a plugin.

Regards

Falk

[Falk Eckert]

No problem.

to copy:

private void updateCustomField(Long customFieldId, Object value, Issue issue) {
	IssueManager issueManager = ComponentManager.getInstance().getIssueManager();
	CustomFieldManager cfManager = ComponentManager.getInstance().getCustomFieldManager();
	MutableIssue mutableissue = issueManager.getIssueObject(issue.getKey());
	CustomField cf = cfManager.getCustomFieldObject(customFieldId);
	mutableissue.setCustomFieldValue(cf, value);
}

Get Value:

com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes
value1 = getCustomFieldValueObject(de.enums.ScoringField.SCORING_FIELD1.getId(), issue);

de.plugin:wilken-total-score-readonly-custom-field
value2 = getCustomFieldValueObject(de.enums.CustomField.TOTAL_SCORE.getId(), issue);

The copy works. I get the error during clone an issue.

Regards

Falk

[Falk Eckert]

Hello,

thx for the answer.

The integrity checker found no inconsistencie. An other idea?

Regards

Falk

[RambanamP]

what are the custom field type? i mean source and destination field types!

if is it possible share your code it will help to debug

[darylchuah]

Hi Falk

Have you try to perform integrity checker see whether does it helps or not ?

Make sure you select all and fix any inconsistent data.