B please, On Sat 19 Aug 2017 at 06:54, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi, > > so based on the feedback I will go back to INFRA and let them configure > a separate Configuration type "Maven Issue Type Scheme" which contains > the issue type "Dependency Upgrade"... > > Kind regards > Karl Heinz Marbaise > > On 18/08/17 20:52, Karl Heinz Marbaise wrote: > > Hi to all, > > > > I have realized that in MASSEMBLY it is possible to define an issue Type > > "Dependency Upgrade" which is very feasible for our projects... > > > > So I have asked INFRA[1] if we could have that for our other JIRA > > projects as well....So the now we can decide between three options: > > > > > > A) switch your other schemes to match MASSEMBLY - meaning in addition to > > getting 'Dependency Upgrade' you also get add additional 30+ others you > > dont use. > > > > B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the > > default. > > > > C) Nothing. > > > > > > So I would vote for option "B" ...The question is what do you think? > > Which options would you like to use in JIRA ? > > > > > > Kind regards > > Karl Heinz Marbaise > > > > More details in the issue. > > > > [1]: https://issues.apache.org/jira/browse/INFRA-14898 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
