Answers.Body: <p>The Github repo for this extension lives here:
  <a href="https://github.com/progressivetech/net.ourpowerbase.sumfields" rel="nofollow noreferrer">https://github.com/progressivetech/net.ourpowerbase.sumfields</a>
  [and has an Issues tab]</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-10T16:24:12.063Z
Answers.Text: Thanks for answering KarinG. Question is raised (and answered) via github: https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/24
Answers.UserDisplayName: Jamie
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-25T22:20:31.233Z
Answers.Text: @Jamie I think the issue is still open as the bug still persists on 4.7.14.
Answers.UserDisplayName: Aivars
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-08T13:25:14.757Z
Answers.LastActivityDate: 2017-02-08T13:25:14.757Z
Answers.UserDisplayName: KarinG - Semper IT
Answers.Body: <p>As KarinG pointed out, best way is probably to raise the issue in GitHub: <a href="https://github.com/progressivetech/net.ourpowerbase.sumfields" rel="nofollow noreferrer">https://github.com/progressivetech/net.ourpowerbase.sumfields</a>
  In general, if someone created and shared an extension it does not automatically mean they will fix all bugs you report. It might mean they come back to you and ask if you would fund the fix. Just to manage your expectations :-)....</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-08T13:27:12.200Z
Answers.LastActivityDate: 2017-02-08T13:27:12.200Z
Answers.UserDisplayName: ErikH - CiviCooP
Body: <p>Where can I submit the bug for the Summary Fields extension?</p>
  
  <p>It seems that the Summary Fields extension has an issue with Relative Dates. In <em>Advanced Search</em> I choose the <strong>Date of Last Contribution</strong> as <strong>Last 60 days including today</strong>. When I go back to saved Smart Group later, the <em>relative date</em> is replaced with <em>fixed date</em> (when the group was created).</p>
  
  <p><a href="https://i.sstatic.net/VvBet.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/VvBet.jpg" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-08T19:55:39.243Z
Comments.Text: We did a bunch of work on ensuring that relative dates get saved as relative dates. I think the outcome was an extension, but objective was to improve on that and get it pushed back to core. not sure how easily it would apply to Summary Fields but may give someone a head start.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-08T20:26:47.330Z
Comments.Text: What extension are you referring to?
Comments.UserDisplayName: Aivars
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-09T00:32:06.227Z
Comments.Text: hasn't been published yet as still in QA phase afaik
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-09T00:32:40.357Z
Comments.Text: if it gets pushed as a PR to core I will update this with JIRA ticket
Comments.UserDisplayName: petednz - fuzion
Tags: <issues><summaryfields>
Title: Where do I submit bug for summary fields extension?
ThreadText: # Where do I submit bug for summary fields extension?
  
  (Asked by: username_0 on 2017-02-08)
  
  Where can I submit the bug for the Summary Fields extension?
  
  It seems that the Summary Fields extension has an issue with Relative Dates. In *Advanced Search* I choose the **Date of Last Contribution** as **Last 60 days including today**. When I go back to saved Smart Group later, the *relative date* is replaced with *fixed date* (when the group was created).
  
  [![enter image description here](https://i.sstatic.net/VvBet.jpg)](https://i.sstatic.net/VvBet.jpg)
  
  **Tags:** issues, summaryfields
  
  > **Comments:**
  > **username_1**: We did a bunch of work on ensuring that relative dates get saved as relative dates. I think the outcome was an extension, but objective was to improve on that and get it pushed back to core. not sure how easily it would apply to Summary Fields but may give someone a head start.  
  > **username_0**: What extension are you referring to?  
  > **username_1**: hasn't been published yet as still in QA phase afaik  
  > **username_1**: if it gets pushed as a PR to core I will update this with JIRA ticket  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-02-08. Score: 1 | Accepted answer
  
  The Github repo for this extension lives here:
  <https://github.com/progressivetech/net.ourpowerbase.sumfields>
  [and has an Issues tab]
  
  > **Comments:**
  > **username_3**: Thanks for answering KarinG. Question is raised (and answered) via github: https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/24  
  > **username_0**: @username_3 I think the issue is still open as the bug still persists on 4.7.14.  
  
  ---
  
  ### Answer by username_4 on 2017-02-08. Score: 2
  
  As KarinG pointed out, best way is probably to raise the issue in GitHub: <https://github.com/progressivetech/net.ourpowerbase.sumfields>
  In general, if someone created and shared an extension it does not automatically mean they will fix all bugs you report. It might mean they come back to you and ask if you would fund the fix. Just to manage your expectations :-)....
  
  
  ---
  
  