Re: [E] RE: Jira tickets fields

Anil Belur

+1, It would also be good if these fields (description) can have some kind of default templates, so its easier for users to raise any issue and provide comprehensive information in the ticket. reducing the challenge-response. 

On Thu, Mar 25, 2021 at 2:09 AM navid.ghazisaidi via <> wrote:

I forgot that, thanks for reminding me, Guillaume!


Should we put it under ?






From: "guillaume.lambert@..." <guillaume.lambert@...>
Date: Wednesday, March 24, 2021 at 3:28 AM
To: Navid <navid.ghazisaidi@...>, "ODL Docs (documentation@...)" <documentation@...>, "TSC@..." <TSC@...>
Cc: "Casey Cain (ccain@...)" <ccain@...>, Daniel de la Rosa <ddelarosa0707@...>
Subject: [E] RE: Jira tickets fields


Thanks Navid


For information, most of best practices have now been migrated to the documentation contributor guides







De : TSC@... [mailto:TSC@...] De la part de navid.ghazisaidi via
Envoyé : mardi 23 mars 2021 21:08
À : ODL Docs (documentation@...); TSC@...
Cc : Casey Cain (ccain@...); Daniel de la Rosa
Objet : [OpenDaylight TSC] Jira tickets fields


Hi All,


Here is the list of fields I believe we should make them mandatory in any jira ticket. I have added description with some example values for each field. As mentioned in our last TSC call, this may help automating the project release tracking and release notes publication.


please let me know what your thoughts are.


We should also find a good place in wiki to publish it. Maybe under Best Practices (







description: project name

values: aaa/bgpcep/controller/daexim/distribution/infrautils/jsonrpc/lispflowmapping/netconf/netvirt/openflowplugin/ovsdb/serviceutils/tpce



description: the importance of ticket

values: Highest, High, Medium, Low, Lowest



description: issue type

values: Bug/New Feature/Task/Improvement/Deprecate



description: the status of ticket

values: Open/In Progress/In Review/Confirmed/Verified/Resolved/Closed/Done/Open



description: the version that the issue was seen (it’s only applicable to bugs)

values: aluminum/silicon/etc.; “None” to be used for anything other than “Bug”



description: the version that includes the bug fix, new feature, behavior/feature change (improvement), or deprecated feature (the first time that the feature is being disappeared)

values: aluminum/silicon/etc.



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

Join { to automatically receive all group messages.