Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

...

Issue #JiraDescription
1

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-332

Audio capture option is not presented, can only upload. Likely not much to be done about this, as it may depend on Firefox not sending the same Android Intents as Chrome. This is a previously known issue.

2

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keyFLUID-6412

The Orator highlighting does not appear at all. This is a previously known issue.

3

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-420

Safari can navigate back through history after publishing
4

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-423

After traversing backward through history in the story editor and refreshing the page, can navigate forward.
5

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-460

iPad: Uploading freshly-captured image, the block editor preview did not appear, though the file uploaded and showed in the story preview just fine. Issue went away after capturing a new photo
6

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-461

Stories can no longer be published with no content (and no blocks added), so Test 1 will always fail. It appears to publish successfully, but since the localStorage ID was null, the author is redirected to the View page with a story ID of null afterwards, which of course fails.

Consider removing this test from the grid, or adding a check for null story before publishing, and then adjusting this test to reflect the check

7

Jira Legacy
serverFluid Project Issue TrackerSystem JIRA
serverId2e29aa46e31a5874-ea43167a-32773fb1-bcd5ab47-0aa8908c274afcf749dd6c07
keySJRK-462

Since accounts are not enabled on the staging site, Test 19 is no longer usable. Either enable accounts on the Staging site (needs a Jira + work) or remove this test