Defect ID Summary Severity

Flash collection throws error "Unable to perform

12608 PUBLISH operation" on clicking publish 2-High
Duplicate company tags appear in a Flash
12609 Collection 3-Medium

12610 Re-order Screen issues on Today's Flashes 3-Medium

12611 UI Issue for Todays Flashes 4-Low

Todays Flashes gets created even if there are no

12612 flashes been published between the time interval 3-Medium
Performance Issue: Todays Flashes takes nearly
12613 20-30 secs to load 3-Medium

Control is not getting navigated to the selected

Flash while clicking Flash headline on Re-order
12614 screen 3-Medium

12615 Todays Flash generation is not consistent 3-Medium

Flash articles in Todays Flashes can be deleted or
12616 inserted 3-Medium
Todays Flash article appear in EMSPlus but wiki
12617 says destination as only Bloomberg and Reuters 3-Medium
Some Flash collections are not showing up
12623 READY button. 3-Medium
Remove the Company Name from Flash
12624 Collection editing page and reorder screen 4-Low
Todays Flashes article type do not have the word
12630 (European) next to its name 4-Low

Today's Flashes are displayed as Locked by

12637 gcc_europe_system 4-Low
Reorder button becomes enabled on Published
12640 articles 3-Medium

History section shows the username as 'System'

12650 for Today's Flashes article 4-Low
Default Region associated with the Today's Flash
12664 articles are not getting displayed in the XMLs 3-Medium
Comment Validity
Clearly a documentum issue, in Dev it is working. In QA not
working. Because when build is done, it was not effected
properly. No code change was done. Invalid

It is the edge case, I missed to cover it in test case. Valid

It is the regression issue that has been there wherever we have
reorder button regardless of article type i.e. also happens when
reordering Market Mover Collection articles. Invalid
Though it is a low priority issue, I agree it is my mistake. I wasn't
sure whether it was to be there. Valid
Job is supposed to run only once a day. For the sake of testing,
Qas changed the time interval to make the job run every 15 mins,
it will obviously take the articles that were published over the day. Invalid
It is the first ever bigger collections introduced in the application.
Application is not designed with performance in mind. Invalid
It is the new feature needed for the application. It is the question
that we needed to ask Claudia, client for the application. QA was
insistent that it should be played in the next release. Then was
asked to finally play this feature. Invalid
Job was in error state. This can happen, if the application is
shutting down when the job has started. No code changed
needed. It will get picked up automatically. Invalid
it is the framework wide feature, it is how it exists for all collection
articles Invalid

It was the requirement Invalid

It was not reproducible by himself in front of me. Invalid

It is the enhancement they needed. This requirement was arised
when the story was dev complete. Invalid
It is the enhancement they needed. This requirement was arised
when the story was dev complete. Invalid
It is pre production bug, they did the build to pre-production when
I was halfway through working on the bug 12611and the code
changes that were checked in were migrated over to pre-
production, even though it was incomplete. Invalid
It is the framework wide regression bug. It was found only when
they tested story 790 Invalid
It is decided in dev huddle that we have to use System as the
username for articles that are generated by the jobs. After doing
it, we decided that we will rollback the code to make 'Gcc System'
as the username as it was to be consistent with existing articels Invalid
This area was worked on by another developer here, who missed
out adding tags attribute for regions for screen_config xml file. Valid