Answers.Body: <p>I think I have seen this before when the volunteer opportunity has no end date. When creating the opportunity, did you select "Open-Ended" for the "Schedule Type?"</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T22:40:58.057Z
Answers.Text: All the opportunities are "Set Shifts".  They have a date and duration.  There is no place to define and end date, just the start date/time and duration.
Answers.UserDisplayName: Ron Gridley
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-22T13:31:03.753Z
Answers.Text: As I recall, the duration is used to calculate the end date after which the assignment should fall off the roster. I suppose I could be wrong about that, and that only opportunities for which an end date is explicitly defined (i.e., not "Set Shifts") are removed from the roster. Whether it is a bug (e.g., bad calculation) or an unimplemented feature, I don't think you'll be able to change the behavior without changing the code.
Answers.UserDisplayName: universalhandle
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T14:01:30.033Z
Answers.LastActivityDate: 2017-05-19T14:01:30.033Z
Answers.UserDisplayName: universalhandle
Body: <p>The View Volunteer Roster for a CiviVolunteer Project indicates it should only be displaying the Assignments for the current day and future days.  However, it lists the assignments which are in the past.  How do we eliminate the past assignments?</p>
  
  <p>In addition, the "Back to Manage Volunteer Projects" button at the bottom of the window does not work.</p>
  
  <p>Drupal - 7.54
  CiviCRM - 4.7.17
  CiviVolunteer Extention - 4.6-2.2.1</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-18T20:40:32.060Z
Comments.Text: I had a go at digging out the link from dmaster but at http://dmaster.demo.civicrm.org/civicrm/vol/#/volunteer/manage I get "API permission check failed for VolunteerUtil/getbeneficiaries call; insufficient permission: require edit own volunteer projects". May need raising somewhere - will flag on chat.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-19T22:43:25.780Z
Comments.Text: I am doing this as a Administrator and have every permission available on.
Comments.UserDisplayName: Ron Gridley
Tags: <civivolunteer>
Title: CiviVolunteer - View Volunteer Roster
ThreadText: # CiviVolunteer - View Volunteer Roster
  
  (Asked by: username_0 on 2017-05-18)
  
  The View Volunteer Roster for a CiviVolunteer Project indicates it should only be displaying the Assignments for the current day and future days. However, it lists the assignments which are in the past. How do we eliminate the past assignments?
  
  In addition, the "Back to Manage Volunteer Projects" button at the bottom of the window does not work.
  
  Drupal - 7.54
  CiviCRM - 4.7.17
  CiviVolunteer Extention - 4.6-2.2.1
  
  **Tags:** civivolunteer
  
  > **Comments:**
  > **username_1**: I had a go at digging out the link from dmaster but at http://dmaster.demo.civicrm.org/civicrm/vol/#/volunteer/manage I get "API permission check failed for VolunteerUtil/getbeneficiaries call; insufficient permission: require edit own volunteer projects". May need raising somewhere - will flag on chat.  
  > **username_0**: I am doing this as a Administrator and have every permission available on.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-05-19. Score: 1
  
  I think I have seen this before when the volunteer opportunity has no end date. When creating the opportunity, did you select "Open-Ended" for the "Schedule Type?"
  
  > **Comments:**
  > **username_0**: All the opportunities are "Set Shifts".  They have a date and duration.  There is no place to define and end date, just the start date/time and duration.  
  > **username_2**: As I recall, the duration is used to calculate the end date after which the assignment should fall off the roster. I suppose I could be wrong about that, and that only opportunities for which an end date is explicitly defined (i.e., not "Set Shifts") are removed from the roster. Whether it is a bug (e.g., bad calculation) or an unimplemented feature, I don't think you'll be able to change the behavior without changing the code.  
  
  ---
  
  