Actions
Bug #22075
closeddocumentation includes allow list of html tags in Workbench
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
Story points:
-
Release:
Release relationship:
Auto
Updated by Peter Amstutz 3 months ago
- Assigned To set to Peter Amstutz
- Subject changed from Allow list for html tags documentation to documentation includes allow list of html tags in Workbench
Updated by Peter Amstutz 3 months ago
- Target version changed from Development 2024-09-25 sprint to Development 2024-10-09 sprint
Updated by Peter Amstutz 2 months ago
- Target version changed from Development 2024-10-09 sprint to Development 2024-10-23 sprint
Updated by Peter Amstutz 2 months ago
- Status changed from New to In Progress
22075-html-tag-doc @ 1be1190dab89770f1042eae37c0e380048c08906
Updated by Peter Amstutz 2 months ago
22075-html-tag-doc @ 0e8f5a456540725f707bb47ab393cd8a5fa0e504
Updated by Brett Smith 2 months ago
It would be good to update the discovery document description fields with additional information as appropriate too.
Updated by Peter Amstutz 2 months ago
22075-html-tag-doc @ e70a52135f2dd38b41d72e3a864f2fe1bd2cdb9f
- All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
- Lists valid HTML tags in the API documentation
- Adds a new "Descriptions and metadata" section when talking about projects.
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- n/a
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- yes
- New or changed UX/UX and has gotten feedback from stakeholders.
- n/a
- Documentation has been updated.
- yes
- Behaves appropriately at the intended scale (describe intended scale).
- documentation change only.
- Considered backwards and forwards compatibility issues between client and server.
- documentation change only.
- Follows our coding standards and GUI style guidelines.
- yes
Updated by Lucas Di Pentima 2 months ago
- Related to
modified_by_client_uuid
not being included in API's responses anymore: The Java SDK might need some updating, as it seems it still expects this field.
Changes LGTM, thanks!
Updated by Peter Amstutz 2 months ago
- Related to Bug #22224: Remove obsolete fields from java sdk added
Updated by Peter Amstutz 2 months ago
Added #22224 to update the Java SDK. On first glance, I don't think it will produce any errors on missing fields, they will just be set to null, and it's almost certainly the case no one is using them.
Updated by Peter Amstutz 2 months ago
- Status changed from In Progress to Resolved
Actions