"Rejected" text state breaks the new editor

Description

To implement:

  • show rejected state, with the option to use a less "harsh" label than "rejected" (maybe like "fix this")

  • includes colour of middle bar

  • includes extra item on the filtering bar

  • the translation progress bar should show the rejected count

Created attachment 1049070
Screenshot of error

Description of problem:
Rejecting a textflow entry in the old editor, breaks that same entity in the new editor

Version-Release number of selected component (if applicable):
3.7

How reproducible:
Easy always

Steps to Reproduce:
1. Login and go to a project, version, language, document
2. Translate an entry, click save as fuzzy
3. Reject that same entry
4. Click "Try the new editor"
5. Find that entry

Actual results:
The editor shows it as grey (untranslated?) and the Save As button doesn't show

Expected results:
Should behave as any other state

Additional info:

Environment

None

Activity

Show:
Alex Eng
August 25, 2016, 11:43 PM

Good one.

`restrict comments to developers`, restrict in where?


Can you update the color in the PR?

Kathryn Gough
August 25, 2016, 11:38 PM

Go with this: #FFA800
It's the orange I've been using for the style guide
https://github.com/zanata/zanata-styleguide

Btw , , I don't seem to have permissions to restrict comments to developers (again).

David Mason
August 25, 2016, 6:56 AM

I just used the rejected colour that was already in the css for the new editor. Could you review the appearance and let me know if I should use a different colour?

Damian Jansen
August 12, 2016, 3:17 AM

Still in 3.9.3

Ready for Release

Assignee

David Mason

Reporter

Damian Jansen

Labels

None

Tested Version/s

None

Story Points

3

Components

Sprint

None

Fix versions

Affects versions

Priority

High