Custom Field to insert Ticket-Id to establish an effective Workflow

[lukmay]

What is the current Problem?

Currently, Emails are sent to the Issue Tracker of the Open Data Hub when Issues are created in the Beacon Web App (in the future also when the issue is updated) The problem is without a Ticket-Id in the Email-Subject, all mails have to get merged manually in the Tracker. To avoid this Problem, the Email-Subject has to contain the Ticket-Id.

What Feature is requested?

A Custom field in the Beacons Web App to insert the Ticket-Id into the Backend. After assigning the Ticket-Id to a beacon. All mails created by updates on this Beacon should contain the Ticket-Id in the Email-Subject.

So the problem described above can be solved and automated with inserting the Ticket-Id once.

[davidebz]

Hi lukmay, which format should the ticket-id have in the e-mail, so that it can be automatically recognized by the Tracker? Let please provide me an example, thanks!

[lukmay]

Hi @davidebz, an Example for the format could be this: [issues.opendatahub.bz.it #7140] so the format is: [issues.opendatahub.bz.it #<TICKET_ID>]

Further information:

• it doesn't matter where this stamp is placed in the subject
• the Ticket Id is not limited to 4 chars, so it will increase in future to 5 and beyond.

Thank you!

[davidebz]

@lukmay Very clear, thank you very much

[sseppi]

@lukmay we deployed the functionality in testing at the following link:

https://admin.beacon.testingmachine.eu

Can you please test and see if everything works well also on the Request Tracker side and let us know till the end of this week?

[lukmay]

@sseppi I opened 2 Issues about what I found while testing:

106 #105

[sseppi]

@lukmay OK, thank you!