Working on this now.. thanks! Jess
On Fri Jan 05 08:17:31 2018, frank.obr...@amdocs.com wrote: > Jessica, > Hi, JIRA currently is broken on the new validation field - we are > not able to add any new issues - could we get this addressed ASAP, > either temporarily reverse the change and retest it before > reintroducing it or temporarily auto-populating it > > Thank you > /michael > > -----Original Message----- > From: ONAP Helpdesk via RT [mailto:onap- > helpd...@rt.linuxfoundation.org] > Sent: Friday, January 5, 2018 00:44 > To: Michael O'Brien <frank.obr...@amdocs.com> > Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA > on mandatory "Affects Version" introduced today > > Greetings, > > Your support ticket regarding: > "Unable to create new JIRA on mandatory "Affects Version" > introduced today", has been entered in our ticket tracker. A summary > of your ticket appears below. > > If you have any follow-up related to this issue, please reply to this > email. > > You may also follow up on your open tickets by visiting > https://rt.linuxfoundation.org/ -- if you have not logged into RT > before, you will need to follow the "Forgot your password" link to set > an RT password. > > -- > The Linux Foundation Support Team > > > ------------------------------------------------------------------------- > LF, > Hi, I totally agree with the new mandatory field "affects version" > - however I have tried adjusting the "configure fields" section and an > unable to raise any Epic or Story anymore because of the blocking > error on this field - which does not show on the create issue screen. > Setting the "Fix Version/s" field does not help. > Can you adjust the "Create Issue" screen so we can fill in this > mandatory field > > > [cid:image002.jpg@01D385BE.48F088C0] > thank you > /Michael > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
