|
|
|
In the meantime, I'm using JIRA's RSS comment feeds like this:
Available from any column view, just look for "RSS ( Issues | Comments )". My email on the JIRA profile is also blank, but the preferences screen tells me I will be emailed with any comments on my issues! How does that work?
Looking at existing info on this (I earlier asked Rob), there are some internal hopes that we'd be able to move towards an auth system like OpenID in the future. It'd be great to be able to login to secondlife.com/account and automatically be logged in here and on the wiki.
@Marion: it doesn't work at present, sorry. Keywords: watch list watching notify
Can we raise the priority of this to critical? I think this is the one thing that's really holding back widespread adoption of Jira. If we had this, people would be able to come in occasionally to report issues and still follow their issues without having to sift through ALL issues every day. Issues wouldn't get lost just by being closed, which could help combat incorrect closure of issues.
I have an (imperfect) workaround to follow recent activity on Jira. I set up and saved a filter called "Recent Activity" that is set to show all issues that have been Updated or Created within the past two days. Sometimes this doesn't catch all comments or other actions on an issue, though. WorkingOnIt, maybe you can steal my filter and make it public. Until there is IMs or e-mail notifications, there is the JIRA client that works very well to handle these concerns.
One possible workaround to watch all your own issues would be to use the "Find Issues" link at the top of the page to search for issues, filling your own name into the "Reporter" field. JIRA automatically generates a single feed of all your issues (not the individual issue's comments Feed as WorkingOnIt mentioned). Both Safari and Firefox will recognize the feed, displaying an RSS feed icon in the browser's address bar. If you click on that RSS icon in the address bar, by default Firefox and Safari will handle the feed where you can subscribe to it. If you have an RSS reader, you could past that link into your reader and use that to watch your issues. I have noticed that some readers might handle the feed differently – Firefox doesn't show the comments on the feed, but on my Mac where I use NetNewsWire, it does show the comments.
Discovered that JIRA's RSS feed is not compliant with the RSS 0.92 standard, so newsreaders may not parse the feed correctly, particularly comments. My workaround may not work well after all. More information on Atlassian's public JIRA, issue JRA-9953.
Sorry for the late reply on this, this continues to be a frustration.
@Lex: Many good points, and I agree! I don't have any objections with raising this, but am not sure how quickly actionable it is. Nevertheless, we get asked about this and @Dzonatas: I didn't think Almworks' JIRA client ( http://almworks.com/jiraclient/overview.html @Simon: Thanks for the ideas. Better match with internal issue. We hope to have /something/ on this front soon.
We've made some under the hood changes that inch us closer to having a solution here. However, the folks working on this have been sidetracked by other critical projects (such as keeping up with the rising load of jira and wiki). Email me in a month if there's no progress or status update on this.
@WorkingOnIT: The JIRA Client does work, it's just that it's limited to read only.
Relating to a note I made earlier:
Holy crap! We appear to have watch lists... and I just got this email for a comment I left:
Date: Sat, 22 Sep 2007 09:08:08 -0700 (PDT) [ Lex Neva commented on Winter, that's an interesting theory, but I'm pretty sure that's not how it > disabling "Show Selection Beam" makes beam render incorrectly for others Lex, this is indeed fixed. This means that you will automatically receive email updates whenever an issue you filed is updated, or when an issue assigned to you is updated.
Additionally, you may now watch issues that you didn't file by adding yourself to the watch list (select the "Watch it" link in the lower left) There is one substantial caveat. This was the result of a manual one-time push of email addresses which required downtime to accomplish (ugh). We don't yet have automatic synchronization in place, so people who have never logged into JIRA won't be able to get emails until we sync databases again. Part of the reason for the delay in enabling this feature in the first place is that we were holding out for the automatic solution, and only recently broke down and accepted the manual solution as a temporary workaround. So, we'll need your help working with new JIRA users who will understandably be frustrated with the lack of this capability. Next week, we'll get an estimate for when automatic synchronization will be in place, whether or not subsequent manual syncs will be necessary, and how frequently we'll be doing those. There's not yet a tracking issue for this problem, but I would not mind if someone filed this. I've gone ahead and created
Thanks for your work on this. I wish we had the perfect solution, and I'm a |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Sub-task
Resolved
Critical
This would save me a lot of time digging through my queue of issues awaiting replies.
We have a known issue with auto-populating the email field, which is why it hasn't been done yet, so I'm linking this to the internal issue ID...