Comments
- 1-6 of 6
It's not entirely intuitive (or ideal), but it is possible. If you setup a subscription where the 'where they have been' category has your desired criteria, and you leave the 'they have changed to' as defaults of 'any' it will return changes to descriptions. The drawback is you're literally going to get updates to any attribute of the card, but I haven't figured out a way to do it other than this.
Yup, I think that would cover the largest issue we've had with transitions. The 'per transition' customization can also be accomodated through the use of specific card properties that are only valid at certain times and have certain values, so I think with tooltips, the overhead of making a custom message per transition is more trouble than it's worth.
Thanks for the info!
Sorry, out of the loop for a bit. Just getting back to this.
You could rephrase the requirement that way if you like. It ends up being the same I believe, just two ways of looking at it. The key is that I want to see the same card twice, once under each parent.
We're not tracking dependencies really. Our product has new development, maintenance and special efforts all going on at the same time. I guess you could say it's a 'project' within the 'product'. We're really using mingle as a product management rather than project management tool. So for instance, we have small 'sub projects' one for marketing, one for the VP for his pet project, etc. And we track those in a special tree and card called 'Work Effort'. You could just as easily call it 'sub project'. Basically it's just a logical grouping of stories that has some value to the business. We don't separate the sprints based on them though. In any one sprint, we may have work ongoing that logically falls into several 'sub projects'. It's just a way for us to report on progress to multiple reporting areas in a way that makes sense to them. Does that make sense?
It seems as if the app is bound to a specific project within Mingle. What if I'm a member of multiple projects and need to track murmurs for all of them?
Also, I'd like to echo the request for pop up notifications of new murmurs. That would be very useful.
- how are you and your team using Murmurs?
- For now only via the murmur wall, and only a few of us are comfortable with it. We're hoping this changes soon.
- what information do you share via Murmurs?
- Primarily status updates on development or requests for updates to cards. Not all of us use subscriptions, so the murmur wall acts as a central point for people to know 'when things change'.
- We're trying to get better about broadening our discussion and using it for team building. We're a distributed team, so relationships and communication are key. We're still working on this part as not everyone is entirely comfortable with new tools or social media.
- I periodically use it for announcements / reminders of upcoming items. Retrospectives, UAT, etc. In the future we hope it reduces our need for email and IM conversation and becomes a 'whole project' solution where we discuss everyting from daily activities to status updates to process changes and improvements.
- how often do you murmur?
- Between 5 and 10 times per week currently.
- how long are your murmurs?
- anywhere between 1 and 5 sentences, often referencing story cards.
- do you use the Jabber chat room integration?
- No, but that's due to territorial issues with our internal jabber server. We're considering an external solution.
- do you have feature requests for Murmurs?
- Yes, integrate with subscriptions so when cards I'm subscribed to are murmured about I'm notified, similar to how comments on a card work (this is also in the feature request forum).
- how are you and your team using Murmurs?
Also, are there any plans to somehow incorporate murmurs into the subscriptions? Ideally, when someone's name or user ID is mentioned in a murmur, I'd like to be able to auto notify that person via email or feed. Just a thought.