Thanks. I don't know how to make those customizations either.
On Mon, Apr 11, 2016 at 8:18 PM, Sean Zhong <[email protected]> wrote: > I have created a request on INFRA to do the JIRA customization. > > https://issues.apache.org/jira/browse/INFRA-11656 > > On Tue, Apr 5, 2016 at 4:45 PM, Sean Zhong <[email protected]> wrote: > > > @Andrew, > > > > It seems I don't have permission to do operation like: > > > > 1. Everyone can report the issue and change the issue assignee. > > 2. Add a new field called “Issue Links” so that we can link the pull > > request here. Like: https://issues.apache.org/jira/browse/SPARK-14359 > > > > The functions are locked. > > > > > > On Tue, Apr 5, 2016 at 2:57 PM, Weihua Jiang <[email protected]> > wrote: > > > >> +1. > >> > >> > >> > >> > >> 在 16/4/5 下午2:55，“Sean Zhong”<[email protected]> 写入: > >> > >> >Jira customization allows us to add new "required field", "optional > >> field" > >> >for new issue submission, and also allow us to define component list, > >> and > >> >etc... > >> > > >> >Here are several customization that make sense to me, please contribute > >> >your thoughts on this: > >> > > >> >1. Add a field called “Issue Links” so that we can link the pull > request > >> >here. > >> >Like how Spark does: https://issues.apache.org/jira/browse/SPARK-14359 > >> > > >> >2. Create component by following the list at > >> >https://github.com/gearpump/gearpump/labels > >> >akkastream, build system, core dashboard docs kafka performance > >> restapi > >> > scalajs security storage storm transaction use case yarn > >> > > >> >3. Everyone can report the issue and change the issue assignee. > >> > > >> >Do these three items make sense to you? Please add to the list if you > >> have > >> >suggestions. > >> > > >> >Sean > >> > >> > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
