-
Notifications
You must be signed in to change notification settings - Fork 11
Issues
is:issue state:open
is:issue state:open
Issue creation is restricted in this repository
Search results
Frontend test cases
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1343 In bcgov/range-web;Frontend testing and bug fixes
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1342 In bcgov/range-web;Regular automatic reminders from MyRA
User StoryFeature written from a Users perspective focused on valueFeature written from a Users perspective focused on valueStatus: Open.#1287 In bcgov/range-web;Annual or twice per year required
User StoryFeature written from a Users perspective focused on valueFeature written from a Users perspective focused on valueStatus: Open.#1286 In bcgov/range-web;Guidance document for clients
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1285 In bcgov/range-web;Show dates in UTC or PST irrespective of client timezone
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1243 In bcgov/range-web;Plan start/End date TimeZone issue
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1242 In bcgov/range-web;- Status: Open.#1166 In bcgov/range-web;
Replacement workflow in the case of a change of tenure holder
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1052 In bcgov/range-web;- Status: Open.#1028 In bcgov/range-web;
Small verbiage change - attachments (PDF and web)
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1019 In bcgov/range-web;v1 myra map
TaskWork that cannot be written as a User StoryWork that cannot be written as a User StoryStatus: Open.#1018 In bcgov/range-web;