-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Redmine Issue Link to Description #1
Comments
At or about line #62 of lib/redmine_ical/patch_redmine_classes.rb
|
Calendar entries already have a URL field and the issue URL is already in there, isn't that enough? |
One would think, I sure thought so too. Before I submitted this bug I looked at the ICS output to verify that field is present and works as expected in many Calendaring applications. However, I'm using this ICS output to my Google Calendar which doesn't use that field. It's one of the on-going issues with Google Calendar - which, I'll admit, is a sub-par calendaring application - and yes they fully ignore users requests to properly implement iCal. So, that leaves it to us, with the only option being to embed that URI into the description field. That URI field is used by Google Calendar or their URI for the event - not the important/authoritative one that we provide. So; this fix is only required cause Google doesn't play nice. I could use another Calendaring application but that Google ones ties so nicely to my phone so I can track my bugs. Of course that would be easier if Google would respect the feed we're providing - they seem to only check every few hours - and may (or may not) refresh after 24. |
Understood, I'll see about it. |
Sweet! thank you. |
Added for clients that don't read the URL field
Just added, I don't have an installation to test it anymore though, so I'll leave that to you. |
It would be awesome if the link in the ics description field had a link back to the redmine issue so that when viewing my calendar I can jump quickly.
The text was updated successfully, but these errors were encountered: