Skip to content
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

As an FS admin I would like an easy way (other than the back button) to get back to the FS Admin page after submitting a content change request through the google form, so that I can easily continue to review the site make other changes if I want to. #597

Open
11 of 12 tasks
ASprinkle opened this issue Mar 15, 2018 · 8 comments
Assignees
Milestone

Comments

@ASprinkle
Copy link

ASprinkle commented Mar 15, 2018

Notes

provide examples of what to change and where they are in the form - TTS will go update the production form itself using that info

Acceptance criteria

  • user can navigate back to the site from the google form

Tasks

  • audit form for staging links and indicate where they are so that they can be updated in prod form (Nate)
  • recommend placement and text for a link back to the production christmas tree permit site (Jane, Nate)
  • tts approval
  • PO approval

Definition of Done

  • Code unit / e2e tested and comply with QWASP
  • No new security vulnerabilities
  • Internal team code review
  • Documentation / readme.md / CircleCI updated
  • Docker updated
  • Compare finished design with mockup
  • Usability tested
@sadlerw
Copy link

sadlerw commented Mar 15, 2018

@ASprinkle we could add a link to the google form back to the staging site for now, but it would have to be updated to point at the production site once the site goes live. /cc @lauraGgit

@ASprinkle
Copy link
Author

Sounds good to me, unless @lauraGgit has a concern with it.

@sadlerw sadlerw added this to the Sprint 12 milestone Mar 21, 2018
@npage123
Copy link

npage123 commented Mar 29, 2018

Proposing adding the following text to the pages within the form. See screenshots for placement reference.

If you don't want to proceed with this form, return to the U.S. Forest Service Christmas trees website at https://forest-service-trees-staging.app.cloud.gov/admin/christmas-trees/season-dates.

Form Page 1
Link already exists.

Form Page 2
597-03

Form Page 3
597-01

Form Page 4
597-02

One more thing, is there an email that gets sent to whomever requests the changes that this text should be added to?

@npage123
Copy link

Along with the newly added links above, the following links (locations included) should be changed before going to production:

Page 1 - Last sentence in following paragraph.
Fill out the form below to request updates to the content on the Christmas tree permit website. If you are a forest service administrator and would like to change your forest's cutting season dates, you can do so by filling out and submitting the form at https://forest-service-trees-staging.app.cloud.gov/admin/christmas-trees/season-dates.

Page 2 - First checkbox
The cutting season dates need to be updated, and I can't access the form at https://forest-service-trees-staging.app.cloud.gov/admin/christmas-trees/season-dates.

@npage123
Copy link

@ASprinkle & @lauraGgit - Please review when you get a chance.

@ASprinkle
Copy link
Author

@npage123
The link you've got on the page that says "We've received your request..." is great. That will take the FS administrator back to the Christmas tree site, which is exactly what the story is asking for!
@lauraGgit is there were a way for the FS administrator to not have to go back through Eauth, since it's implied that they've already done this to get to the google form. Or do they have to go through Eauth since they are leaving the site?

@npage123 There is no email that is sent to the FS admin requesting the change. The email address and First Name, Last Name data is supposed to be sent to the GSA steward so that they can follow up with the FS admin requesting a complex content change.

@lauraGgit
Copy link

@ASprinkle I think it may be hard to get them back to the site without going back through eauth, unfortunately.

@lauraGgit
Copy link

updated the form an the response, moving to staging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants