[Tails-dev] Mide el clima laboral en tu organización.

[Mide el clima laboral de tu empresa para una mejora continua.]

   





 




 Sistema en línea para la medición del clima laboral (organizacional)

 

La medición del clima laboral influye sustancialmente en la productividad, la 
eficiencia, la rotación de personal, la satisfacción del cliente y satisfacción 
en el trabajo esto se puede medir y mejorar evaluando el clima organizacional 
dentro de tu organización, con Smart Clima podrás hacer esto.

 

Los beneficios del sistema son:

*   Diferentes tipos de reportes de resultados (Nivel de satisfacción, por 
departamento). 
*   Monitoreo de los avances en tiempo real. 
*   Configuración de la encuesta a la medida de tus necesidades.
*   Asesoría gratuita de parte de nuestros consultores para la 
configuración y aplicación de la encuesta.


 





 





 



 

 Cotiza el sistema, clic aquí 



 



 

 Más información del sistema 


 






   


Teléfonos


 


Ciudad de México: 01 (55) 5018 0565

Guadalajara, México: 01 (33) 1580 8033

Lada sin costo (México): 01 (800) 022 0362

Bogotá, Colombia: 01 (571) 508 8250

 

 

 Clic aquí, para darse de baja.




 


© 2019 PsicoSmart


 



  

 


___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Proposal: Redmine workflow change

[segfault]

Hi,

intrigeri:
> anonym:
>> intrigeri:
>>> Given we now have "mentions" (@nickname) on our Redmine, for the
>>> majority of cases, when the requested info can presumably be provided
>>> cheaply and quickly, I think we should use mentions and not reassign
>>> the ticket. And when I'm mentioned, if I realize that providing the
>>> requested info needs will take me great amounts of work, I should
>>> do whatever works for me to track this work, be it on a new ticket
>>> or my personal offline organization tools.
> 
>> I quite like this feature and have set up filter rules in my email
>> client for the resulting redmine notifications I receive so I don't
>> miss them. However, I wonder how this works out if you don't do
>> something like that. I also fear that the ad hoc tracking of
>> "mentions" that you propose above is easy to forget.
> 
> I think most of us are in one of these 4 situations:
> 
>  - They notice and track new incoming emails but don't pay much
>attention to tickets reassigned to them on Redmine (note that
>Redmine sends no notification to the new assignee).
> 
>Mentions help. Reassigning does not help (I've seen quite a few
>cases recently where it appears that the new assignee had no idea
>something was expected from them).
> 
>So dropping "Info Needed" is a no-op.

I fall into this category, *but* I think the "Info Needed" field is
still sometimes useful for me. While I at least take notice of all my
Redmine emails, I sometimes get a lot of them (because I also watch some
tickets which are not on my plate, but for which I would like to stay
up-to-date about the progress). And my tracking is not the best, I
sometimes forget to star an email that requires action by me. In this
case it does help if a ticket is assigned to me so that I see it when I
check my assigned tickets on Redmine (which I do rarely, but still).

But I also see that losing track of ones issue by assigning someone for
"Info Needed" is a problem. It would be nice if Redmine would support
multiple assignees for issues, which GitLab does support.

All in all I'm okay with trying to drop the "Info Needed" field and see
how it works out.

Cheers
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Proposal: Redmine workflow change

[intrigeri]

Hi,

I'll wait (at least) one more week and if there's no strong objection,
I'll implement this proposal.

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Proposal: Redmine workflow change

[intrigeri]

Hi,

anonym:
> intrigeri:
>> Given we now have "mentions" (@nickname) on our Redmine, for the
>> majority of cases, when the requested info can presumably be provided
>> cheaply and quickly, I think we should use mentions and not reassign
>> the ticket. And when I'm mentioned, if I realize that providing the
>> requested info needs will take me great amounts of work, I should
>> do whatever works for me to track this work, be it on a new ticket
>> or my personal offline organization tools.

> I quite like this feature and have set up filter rules in my email
> client for the resulting redmine notifications I receive so I don't
> miss them. However, I wonder how this works out if you don't do
> something like that. I also fear that the ad hoc tracking of
> "mentions" that you propose above is easy to forget.

I think most of us are in one of these 4 situations:

 - They notice and track new incoming emails but don't pay much
   attention to tickets reassigned to them on Redmine (note that
   Redmine sends no notification to the new assignee).

   Mentions help. Reassigning does not help (I've seen quite a few
   cases recently where it appears that the new assignee had no idea
   something was expected from them).

   So dropping "Info Needed" is a no-op.

 - They regularly look at their Redmine plate but they won't notice
   incoming email Redmine sends them, unless they set up
   ad-hoc filters.

   Mentions don't help. Reassigning or creating a new subtasks helps.

   So dropping "Info Needed" + reassignment brings a regression.
   To mitigate this:

- We should strongly recommend these folks set up whatever
  filters they need to notice email our Redmine is sending them.
- Creating a dedicated subtask for the info request is an option
  in some cases (I'll discuss this below).
- To address the root cause of the problem and make email
  a communication option that actually works, we should gently
  suggest these folks to unsubscribe from sources of incoming
  email that they don't read, and that swamps them in an inbox
  they barely dare looking at. I guess that's part of self-care
  recommendations we could promote more visibly within Tails :)

 - They pay attention to their Redmine plate and to incoming email.

   All's well, no change here.

 - They don't pay much attention to their Redmine plate and don't
   notice incoming email from Redmine.

   No change here. No ticket tracking system will help. Only social
   processes, such as regular team meetings, have a chance to enable
   successful collaboration & communication.

> I just had a half-baked idea that might have some merit: say I work
> on ticket X and need info about "foo" from intrigeri. Then I just
> create a subticket Y of X called "Info needed: foo" and assign it to
> intri. When intri has posted the information about "foo" to X he can
> then mark Y as resolved.

That's surely a valid option in some cases, mainly: 1) when the
overhead of "just" creating a subtask is justified by the amount of
work needed to fulfil the info request; 2) for those of us who can't
afford paying attention to email Redmine sends them. I don't know how
much of our "Info Needed" usage fits into this category. I want to
keep this option in mind even though I'd rather first tackle the root
cause of the problem, because for (2) this option feels like
a workaround.

Cheers!
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Proposal: Redmine workflow change

[intrigeri]

sajolida:
> intrigeri:
>> So I propose that we drop the "QA Check" field and instead, introduce
>> a "Needs Validation" status.

> Good idea! Works for me.

:)

> What would happen to tickets that go back-and-forth between the main
> author and the reviewer? Would they stay in "Needs Validation" or go
> back-and-forth between "In Progress" and "Needs Validation"?

The latter, as per:

  And if the reviewer requests changes, they would set the status
  back to "In Progress".

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.