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

KB article update existing article : VAMC Facility editing. #15574

Closed
4 of 15 tasks
swirtSJW opened this issue Oct 5, 2023 · 1 comment
Closed
4 of 15 tasks

KB article update existing article : VAMC Facility editing. #15574

swirtSJW opened this issue Oct 5, 2023 · 1 comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Knowledge Base [CMS feature] Knowledge Base Needs refining Issue status sitewide VAMC CMS managed product owned by Facilities team

Comments

@swirtSJW
Copy link
Contributor

swirtSJW commented Oct 5, 2023

Background context

What is the request for?

  • Create new article
    • I have reviewed the Knowledge Base to confirm that an article for this topic does not already exist
  • Update existing article: How to edit a VAMC Facility

If requesting a new article:

Topic Description
Details about the topic. If possible, include an example of a use case or situation that illustrates the topic well.
This issue #14213 moved the mental health facility field to become editable by users and directs users to the KB article, but the KB article does not address the Mental health phone numbers yet. It will need to be added.

Audience
Who is this intended for? Who would need this information? (i.e. All editors, only editors for a particular product, Internal use only, etc.)

  • VAMC facility editors

Is the article associated with an ongoing product or feature update?

Priority or deadline for request

Choose either Deadline or a priority:

  • Deadline: [name the deadline here]
  • Priority:
    • Critical - Without this, there is a large negative impact on the majority of editors causing negative consequences within the CMS; Should be completed as soon as possible
    • High - Without this, there is negative impact on some editors causing negative consequences within the CMS; should be completed within the current sprint
    • Medium - Without this, there is confusion for editors but not causing negative consequences within the CMS; Should be completed within the next 1-2 sprints
    • Low - This is not currently causing confusion for many editors but would be a nice to have or is something that may be more impactful in the future; Should be completed within the next 3-4 sprints

Acceptance Criteria

@swirtSJW swirtSJW added VAMC CMS managed product owned by Facilities team Knowledge Base [CMS feature] Knowledge Base Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status labels Oct 5, 2023
@swirtSJW
Copy link
Contributor Author

swirtSJW commented Oct 5, 2023

Closed as a duplicate of #14217

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Knowledge Base [CMS feature] Knowledge Base Needs refining Issue status sitewide VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

2 participants