It is set when you select which product your request applies to. So the group in charge of that product determine for all RFEs for its group are public or private.
On Wed, Sep 17, 2014 at 8:34 AM, Mike Wawiorko <[email protected]> wrote: > I see this in the RFE. > > --------------------------- > Visibility: > Private > Public requests are visible to all users; Private requests are visible only > to the original submitter. The visibility is automatically set when the > request is created. > --------------------------- > > It says " The visibility is automatically set when the request is created." > Can anyone on the list (IBMer?) explain how the RFE can be made public? I > didn't get any option to do so myself - or I missed it. > > Mike Wawiorko > Please consider the environment before printing this e-mail > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Gibney, Dave > Sent: 16 September 2014 20:22 > To: [email protected] > Subject: Re: EZANS Requirement > > Still private? > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of Lizette Koehler >> Sent: Friday, September 12, 2014 9:03 AM >> To: [email protected] >> Subject: EZANS Requirement >> >> This was posted on the TCPIP List >> >> >> See the RFE number 59073 I've just submitted. >> >> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID >> =59073 >> >> >> Not sure if you can see it - it says 'Private' and I can't seem to >> find any option to make it public. Maybe that happens once it is reviewed by >> IBM. >> >> Mike Wawiorko >> >> Lizette >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > This e-mail and any attachments are confidential and intended solely for the > addressee and may also be privileged or exempt from disclosure under > applicable law. If you are not the addressee, or have received this e-mail in > error, please notify the sender immediately, delete it from your system and > do not copy, disclose or otherwise act upon any part of this e-mail or its > attachments. > > Internet communications are not guaranteed to be secure or virus-free. The > Barclays Group does not accept responsibility for any loss arising from > unauthorised access to, or interference with, any Internet communications by > any third party, or from the transmission of any viruses. Replies to this > e-mail may be monitored by the Barclays Group for operational or business > reasons. > > Any opinion or other information in this e-mail or its attachments that does > not relate to the business of the Barclays Group is personal to the sender > and is not given or endorsed by the Barclays Group. > > Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). > Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. > > Barclays Bank PLC is authorised by the Prudential Regulation Authority and > regulated by the Financial Conduct Authority and the Prudential Regulation > Authority (Financial Services Register No. 122702). > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
