Re: change jira components to be more user friendly
I've had a stab at this - any feedback on extra components? - Brett Brett Porter wrote: Hi, I was wondering what folks though of changing maven-artifact, maven-core, etc in JIRA to be user friendly components like: * error reporting * artifact deployment * artifact resolution etc. These often cover more than one physical component anyway and they are more likely to be initially filled in correctly. No need to change plugins as I think the consensus is to eventually move them out into individual jira projects. Thoughts? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change jira components to be more user friendly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me for changing the components. Comments inline. Jason van Zyl wrote: | On Mon, 2005-11-07 at 10:20 +1100, Brett Porter wrote: | |>Hi, |> |>I was wondering what folks though of changing maven-artifact, |>maven-core, etc in JIRA to be user friendly components like: |> |>* error reporting |>* artifact deployment |>* artifact resolution |> |>etc. | | | +1 | | Anything the user can identify with directly is better. It's too bad we | can't have multiple views so to speak. So the user does what makes sense | to them but we can map that somehow to the component in question. So we | could filter on all the problems in maven-core for example. But the user | being able to file correctly in the first place is probably more | important. | I think this level of classification would be too much to maintain. That is, while it might be useful, I think the effort involved in maintaining the cross references (the user supplies one, devs map that to another) will exceed its value. At any rate, I guess it's all academic, right? Jira doesn't support this, without creating/maintaining a custom field like we did for complexity level, right? | |>These often cover more than one physical component anyway and they are |>more likely to be initially filled in correctly. |> |>No need to change plugins as I think the consensus is to eventually move |>them out into individual jira projects. | | | +1 for plugins in their own projects I'm +1 for project-per-plugin too. | | |>Thoughts? |> |>- Brett |> |>- |>To unsubscribe, e-mail: [EMAIL PROTECTED] |>For additional commands, e-mail: [EMAIL PROTECTED] |> |> -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDcnGkK3h2CZwO/4URAsvMAKCB2FYZ3+jxQPkFVt1QKBsSwm24MwCeKnc4 XhrSsVbOQwnN9pJD+BkqJtM= =SHor -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change jira components to be more user friendly
But the user being able to file correctly in the first place is probably more important. I agree. I'm just wondering then why I never got an answer to my mail on this: http://www.mail-archive.com/dev%40maven.apache.org/msg42387.html -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change jira components to be more user friendly
On Mon, 2005-11-07 at 10:20 +1100, Brett Porter wrote: > Hi, > > I was wondering what folks though of changing maven-artifact, > maven-core, etc in JIRA to be user friendly components like: > > * error reporting > * artifact deployment > * artifact resolution > > etc. +1 Anything the user can identify with directly is better. It's too bad we can't have multiple views so to speak. So the user does what makes sense to them but we can map that somehow to the component in question. So we could filter on all the problems in maven-core for example. But the user being able to file correctly in the first place is probably more important. > These often cover more than one physical component anyway and they are > more likely to be initially filled in correctly. > > No need to change plugins as I think the consensus is to eventually move > them out into individual jira projects. +1 for plugins in their own projects > Thoughts? > > - Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change jira components to be more user friendly
Sounds good to me and, as you said, users won't probably know which component(s) is(are) affected anyway. Cheers, Stéphane On 11/7/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Hi, > > I was wondering what folks though of changing maven-artifact, > maven-core, etc in JIRA to be user friendly components like: > > * error reporting > * artifact deployment > * artifact resolution > > etc. > > These often cover more than one physical component anyway and they are > more likely to be initially filled in correctly. > > No need to change plugins as I think the consensus is to eventually move > them out into individual jira projects. > > Thoughts? > > - Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::.
change jira components to be more user friendly
Hi, I was wondering what folks though of changing maven-artifact, maven-core, etc in JIRA to be user friendly components like: * error reporting * artifact deployment * artifact resolution etc. These often cover more than one physical component anyway and they are more likely to be initially filled in correctly. No need to change plugins as I think the consensus is to eventually move them out into individual jira projects. Thoughts? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
