It should be possible to require entry of fix version when updating status. We would just need to pick which status change meant "merge to release branch" ________________________________________ From: iotivity-dev-bounces at lists.iotivity.org [iotivity-dev-bounces at lists.iotivity.org] on behalf of mats at wichmann.us via RT [[email protected]] Sent: Friday, April 14, 2017 9:18 AM To: uzchoi at samsung.com Cc: iotivity-dev at lists.iotivity.org Subject: [dev] [IoTivity Helpdesk #39845] [linuxfoundation.org #39845] Re: Jira field setting.
On 04/14/2017 07:12 AM, ??? wrote: > Hi C.J. > > There are several jira ticket without fix version field. so that this is not > easy to analyze the release status. > > Can we set the "Fix version/s" filed as mandatory input when we create jira > ticket? > > BR, UZe Choi I think this should be the job of bug triage, and later of release management... the submitter may not be the person in position to decide which release a problem must be fixed in (of course we all want it in the very next one!!! :)) _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev NOTICE: All information in and attached to the e-mails below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message electronic, paper, or otherwise. By transmitting documents via this email: Users, Customers, Suppliers and Vendors collectively acknowledge and agree the transmittal of information via email is voluntary, is offered as a convenience, and is not a secured method of communication; Not to transmit any payment information E.G. credit card, debit card, checking account, wire transfer information, passwords, or sensitive and personal information E.G. Driver's license, DOB, social security, or any other information the user wishes to remain confidential; To transmit only non-confidential information such as plans, pictures and drawings and to assume all risk and liability for and indemnify Lowe's from any claims, losses or damages that may arise from the transmittal of documents or including non-confidential information in the body of an email transmittal. Thank you.
