# data[].attributes.body
DA-1080

Minimize rate limit and credential checks for multiple Twitter networks

# data[].attributes.body
DA-869

Make more understandable error messages for Twitter

# data[].attributes.body
DA-1089
Prepare delivery procedure description

# data[].attributes.body
DA-1087
Prepare Business case description

# data[].attributes.body
DA-1091 Prepare technical design description

# data[].attributes.body
DA-1090 Prepare functional design description

# data[].attributes.body
DA-1086 Replace Instagram collecting mechanism with more efficient (less requests to API)

# data[].attributes.body
2 week sprints
Sprint #9 = 27 story points (4,5 per member)
Sprint #10 = 19 story points (5,4 per member)
Sprint #11 = 12 story points (3,2 per member)
Sprint #12 = 3 story points (<1 per member)
3 week sprints
Sprint #13 = 30 story points (7,5 per member)
Sprint #14 = 43 story points (10,75 per member)
Sprint #15 = 36 story points (9 per member)
Sprint #16 = 8 story points (8 per member)
Sprint #17 = 19 story points (8 per member)
Sprint #18 = 16 story points (6,87 per member)
Sprint #19 = 16 story points (6,87 per member)
Sprint #20 = 12 story points (4,87 per member)
Sprint #21 = 13 story points (5.3 per member)
Sprint #22 = 14 story points (7 per member)
Sprint #23 = 0 story points (0 per member)

# data[].attributes.body
Create mechanism, which will be filtering out earlier disapproved messages from response, when auto-approval option is turned on.

# data[].attributes.body
DA-781

Remove Start service button, as well as Live checkbox.
1) Change solution for fetching configuration to BGScheduler from Queue to SignalR

# data[].attributes.body
DA-1015

Make it possible to use common messaging system in Simple template

# data[].attributes.body
DA-1022

Create separate template with description to provide for external developers to work with

# data[].attributes.body
DA-532

Create description for the template structure from the technical side

# data[].attributes.body
Next sprint
Vladimir (1),
Anton  (0.8),
Zia ? (1) .

Planned 9 user story points.

Total 1.89 .

# data[].attributes.body
DA-759 (Background messages - general)

Add some mechanism to check if streaming is still getting messages or not (exception and restart if any, hub if it still working)

# data[].attributes.body
Planned 13 user story points
Completed 8 user story points
Team: 0, 5 + 0.8  + 1  = 2.33
Velocity:  story points 3.4 per member.

# data[].attributes.body
DA-134

Prepare solution proposal about new app which will allow to organize polls using Twitter

# data[].attributes.body
DA-622 (Priority score by popularity)

Calculating priority of message and provide that information to public template

# data[].attributes.body
DA-508

Make possibility to get messages from the background process for all social medias - Facebook

# data[].attributes.body
DA-343

Make background message collection mechanism

# data[].attributes.body
DA-377

As a user I'd like to add content (messages or pictures) from a Dropbox folder

# data[].attributes.body
DA-495

Statistics for the data we don't have at a moment

https://eptron.atlassian.net/wiki/display/DA/%28STATISTICS%29+Statistics

# data[].attributes.body
DA-617 (Instagram - background)

Process Instagram messages from background process so they could be added to campaign

# data[].attributes.body
DA-618 (Instagram - background)

Start collecting messages from Instagram in background

# data[].attributes.body
DA-623 (Priority score by popularity)

Sequencing of messages on public side

# data[].attributes.body
DA-55 (Priority score by popularity)

As a customer I would like to sort messages based on defined criteria so messages displayed will be more relevant for the viewers

# data[].attributes.body
DA-600 (Dropbox)

Allow user to choose the folder from which campaign should take the data

# data[].attributes.body
DA-613 (Facebook - background)

Make login to FB
1) generalize the mechanism of authorization for all networks

# data[].attributes.body
DA-378

Make possibility to get messages from the background process for all social medias - Instagram

# data[].attributes.body
DA-377

As a user I'd like to add content (messages or pictures) from a Dropbox folder

# data[].attributes.body
DA-599 (Dropbox)

Authorize Dropbox user per campaign

# data[].attributes.body
DA-510 (Dropbox)

Load messages from Dropbox in the background

# data[].attributes.body
DA-499 (Dropbox)

Load one message from user dropbox directory

# data[].attributes.body
DA-619 (Dropbox)

Applying date filter to messages from folder

# data[].attributes.body
DA-768 (Background messages - general)

If there are modifications to network which is collecting messages already, user should have an option to choose what to do with not valid any more messages

# data[].attributes.body
DA-956

Show status of the background streaming for the campaign to user

# data[].attributes.body
DA-1019

Upload custom template (js + html) and load it on public side

# data[].attributes.body
DA-1018

Add custom parameters for the custom template

# data[].attributes.body
DA-1016

Make it possible to use common messaging system in Polaroid template

# data[].attributes.body
DA-1017

Make it possible to use common messaging system in Message Circle template

# data[].attributes.body
Refactor the existing Message Circle template
DA-571

Try to standardize template structure to use external HTML

# data[].attributes.body
DA-1020 (3)

Make it possible to use common messaging system in Mosaic template

# data[].attributes.body
DA-1021

Performance improvement for Message Circle and Polaroid templates on Tronsmart devices

# data[].attributes.body
We should devise a specific pattern, on which all templates should be programmed. Paging component should be taken to SMAppController.

# data[].attributes.body
Make the hyphenation correct in Polaroid, Simple, Message Circle.

# data[].attributes.body
Display long messages in Message Circle in correct way

# data[].attributes.body
Create schema of message handling mechanism in SMAppController