This proposal could improve contributor and user experience, but the proposed change is opt-in.
It does not make the field/state mandatory, hence the existing flows won't be affected if the maintainers do not want to spend time on JIRA updates.
WDYT?
Thanks in advance,
Oleg
IIUC this proposal would allow us to have an intermediate state between In Review and Resolved/Fixed.
+1, I have seen people get confused when an issue is moved to
Resolved/Fixed after a PR is merged yet the fix is not available on
the update center.
(BTW I am not sure what the Closed resolution is for.)
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3BF8cn17%2Bs_5dAHzfK_%3DewW7B%3D0vSGGSiWfE_fBpGwew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
(BTW I am not sure what the Closed resolution is for.)Nobody knows :(Maybe we want to just remove it and merge with Resolved
Am 14.08.2017 um 17:10 schrieb Oleg Nenashev <o.v.ne...@gmail.com>:IIUC this proposal would allow us to have an intermediate state between In Review and Resolved/Fixed.
Exactly+1, I have seen people get confused when an issue is moved to
Resolved/Fixed after a PR is merged yet the fix is not available on
the update center.Good point. Once we have the fix, we will be able to update Jenkins Issue autoupdater to move the
issues to the "Stage Release" state instead of "Resolved".
(BTW I am not sure what the Closed resolution is for.)Nobody knows :(Maybe we want to just remove it and merge with Resolved2017-08-14 17:07 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>:+1, I have seen people get confused when an issue is moved to
Resolved/Fixed after a PR is merged yet the fix is not available on
the update center. IIUC this proposal would allow us to have an
intermediate state between In Review and Resolved/Fixed.
(BTW I am not sure what the Closed resolution is for.)
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3BF8cn17%2Bs_5dAHzfK_%3DewW7B%3D0vSGGSiWfE_fBpGwew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAx%2B8oN8dBU4a59PbrEp8ZnO_YFWBcgB2Y48uOV06_FUw%40mail.gmail.com.
That makes our workflow complex to understand for others. Who is responsible to move the issues from the new state to resolved? If you consider to add another state please make it optional and do not change the default (and simple) workflow for plugin authors.Am 14.08.2017 um 17:10 schrieb Oleg Nenashev <o.v.ne...@gmail.com>:IIUC this proposal would allow us to have an intermediate state between In Review and Resolved/Fixed.
Exactly+1, I have seen people get confused when an issue is moved to
Resolved/Fixed after a PR is merged yet the fix is not available on
the update center.Good point. Once we have the fix, we will be able to update Jenkins Issue autoupdater to move the
issues to the "Stage Release" state instead of "Resolved".Please do not change the current behavior. Most plugin authors do not need such an overly complex workflow. We just fix some issues, make a release and move forward to the next ones.
> Would like to know:
> - New state name? "Stage Release“
I’m not a native speaker but Stage Release seems to be grammatically different from the other ones: Closed, Resolved, In Progress
>
> Please don’t change the default names in Jira, there are so many people that use Jira in other projects.
(BTW I am not sure what the Closed resolution is for.)Nobody knows :(Maybe we want to just remove it and merge with Resolved
Actually Closed is used to mark that an issue actually has been verified to be fixed in a released version. Normally this is done by the reporter (or in other projects by QA).
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4F160C4F-DD13-4B73-948F-668C77DEB0DA%40beckweb.net.
-1 JIRA was designed to have a project per software lifecycle. The fact that we have 1000 plugins in the same JENKINS project breaks all the nice things about JIRA, such as the Fixed For field and Versions, which was designed for this very problem.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a835c953-65a4-44a7-b1f0-55384d0498e9%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
I am merely giving a reasonable response to the proposal, which I think is fair, given I am the component leader on projects cited as benefiting from this change.
The tool we use already makes provisions for the problems outlined. Additional statuses will not add clarity as this is now how JIRA projects are usually used which runs contrary to user expectations of this widely used tool.
Secondly, as someone who spends much time in JIRA who would benefit from tracking such information, the proposed fields cannot be used in conjunction with JIRA reporting functionality such as Created vs Resolved charts, which are very beneficial to those who manage triaging and tracking the health of sub-projects.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/61e48fa9-5b59-4ee8-8e2c-227376c251b7%40googlegroups.com.
Hi all,
As a Jenkins user and contributor, I sometimes have difficulties when I need to understand in which release the fix is available. GitHub commit links from the bot help much, but it requires extra time to navigate across commits and UI. In Jenkins core, Remoting and my plugins I would like to make it more explicit:
I propose to...
- Modify workflow in the JENKINS project:
- Add a "Stage Release" state (or whatever similar name)
- Instead of "In Progress" => "Resolved", contributors can move integrated fixed into the "Stage Release" state.
- It may be helpful for components which do not release the integrated fixes immediately (e.g. Core, its modules, Remoting, Stapler, Blue Ocean, other plugins)
- Add an optional "Released As" field to JIRA (type=String)
- When a contributor moves the issue to "Stage release", "Resolved" or "Closed" state, an optional field appears in the dialog
- If the field is non-empty, it will appear in the ticket header, hence users won't need to look into comments and commit histories
This proposal could improve contributor and user experience, but the proposed change is opt-in.
It does not make the field/state mandatory, hence the existing flows won't be affected if the maintainers do not want to spend time on JIRA updates.
WDYT?
Thanks in advance,
Oleg
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/521bcc90-6ab0-42ec-b6b6-aeb6c225e901%40googlegroups.com.
It would be awesome if the issue updater could fill in the correct value by extracting the Pom version.
Hi all,
As a Jenkins user and contributor, I sometimes have difficulties when I need to understand in which release the fix is available. GitHub commit links from the bot help much, but it requires extra time to navigate across commits and UI. In Jenkins core, Remoting and my plugins I would like to make it more explicit:
I propose to...
- Modify workflow in the JENKINS project:
- Add a "Stage Release" state (or whatever similar name)
- Instead of "In Progress" => "Resolved", contributors can move integrated fixed into the "Stage Release" state.
- It may be helpful for components which do not release the integrated fixes immediately (e.g. Core, its modules, Remoting, Stapler, Blue Ocean, other plugins)
- Add an optional "Released As" field to JIRA (type=String)
- When a contributor moves the issue to "Stage release", "Resolved" or "Closed" state, an optional field appears in the dialog
- If the field is non-empty, it will appear in the ticket header, hence users won't need to look into comments and commit histories
It would be awesome if the issue updater could fill in the correct value by extracting the Pom version.
--This proposal could improve contributor and user experience, but the proposed change is opt-in.
It does not make the field/state mandatory, hence the existing flows won't be affected if the maintainers do not want to spend time on JIRA updates.
WDYT?
Thanks in advance,
Oleg
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/521bcc90-6ab0-42ec-b6b6-aeb6c225e901%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/710C9068-A180-4F72-8CCA-6F27D09287F5%40gmail.com.
We can discuss it, and perhaps work out a complete proposal, but we should not reach a conclusion there, as it excludes too many people unable to be present at the specific time.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/E0EE9A09-C581-4C69-A01E-0986A0196BF8%40beckweb.net.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180212175616.dntzdyauekyb3kps%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/09da1270-4b31-4f27-b627-f5738da25b81%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/09da1270-4b31-4f27-b627-f5738da25b81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/887278D0-A494-477D-AB28-CB7DBC1819EA%40gmail.com.