Closed jknipes closed 2 months ago
Tasks have been refined and this ticket requires input from Platform Product Team, to be executed in a future sprint. Content Team is pausing our work on this and moving it to the Backlog
Changed the Content team's story points to "5" to better align with the Platform Product team's metric
Sprint automation added this to Jul 4th sprint incorrectly. We are removing sprint dates and keeping in backlog pending availability from Product team
We have this scheduled for Sprint 6 (7/18-7/31/2024) @jknipes @laucon Thank you!
7/17 update: we will be reviewing the code in order to determine the owners of the blank content at the bottom of the page (Task step 3)
This ticket seems like it should either be one ticket in a long list of tickets, or it should be folded into one much larger ticket. Why? Well, because each and every page under External Service Integrations has major content issues. Nearly all of them list names. Most have empty headers, formatting errors, and/or jumbled text. This entire section could use an Audit. For quick reference, I have included links to every page in this section below: (NOTE: All pages listed have issues, save for one, but I have included notes to certain issues that jumped out at me while quickly scrolling through. These notes are not an exhaustive list of issues by any means)
@BSmolensky this ticket has now been added to the Q3 2024 Platform Content Team Tech Debt epic. We will create additional tickets for the epic to address this issues found on each page in the External Service Integrations section.
@jknipes - Sounds good.
@jknipes - thank you, I would like to keep all of @BSmolensky's additional tickets as smaller deliverables, and I appreciate you breaking these out! @rmtolmach - FYI
7/22 update: a lot of these will be addressed in our Upstream services objective. We will discuss details when we meet on Tuesday. cc: @LindseySaari @rmtolmach
7/24 update: Brian S is reviewing half of this work as well. @rmtolmach will likely work on it on Friday 7/26.
According to Adrian Rollett and Stephen Barrs, HQS is no longer in use.
ADRIAN: Hey Brian, I don't think the healthquest service is in active use so I'm not sure if it's worth spending time on documenting it. (at)Stephen Barrs do you have any recollection about this? STEPHEN: yep that was part of a Questionnaires pilot that failed successfully (it determined that the product work should not continue)
After consulting with @rmtolmach, HQS page should be archived.
@jennb33 shall we leave this ticket to be closed out by your team?
7/25 update: @rjohnson2011 to confirm that there is no traffic to the VetsAPI. Raise any follow-up items to the team so that future work can be scheduled.
FYI @LindseySaari
According to Adrian Rollett and Stephen Barrs, HQS is no longer in use.
ADRIAN: Hey Brian, I don't think the healthquest service is in active use so I'm not sure if it's worth spending time on documenting it. (at)Stephen Barrs do you have any recollection about this? STEPHEN: yep that was part of a Questionnaires pilot that failed successfully (it determined that the product work should not continue)
After consulting with @rmtolmach, HQS page should be archived.
While all the "Tasks" have not been completed, this ticket is still complete This is due to the fact that the scope of the ticket changed during the review process. We discovered that the page need not exist any longer and should be archived.
So, this ticket is "complete" and we are moving it to close
UPDATE: HQS page has been archived.
Issue Description
Health Quest Service and Authorization Design Doc and many other documents in Confluence use personal names. This is not appropriate on the Platform website because team members roles from time to time, making documents go quickly out of date.
Additionally, there should be no headers without further text.
SME: Rebecca Tolmach
Tasks
CONTENT TEAM:
Acceptance Criteria
[x] This page been updated and is ready to be published
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)