Add a Subscribe Button to the Info Panel

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Content Dashboard
• Labels:
  • dev-feature-flag-off
• Epic Link: tango-cd-info-panel-missing-capabilities
• Sprint: TANGO | #82 DEV | Aug01-Aug15
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/2655

User Story

As a content marketer, I want to subscribe to web content from the content dashboard, so that I am notified when changes are made to that asset.

Design

Figma

Acceptance Criteria

1. A subscribe button must be included in the Info Panel of the Content Dashboard for Web Contents. 
2. Once a user has subscribed to an asset, they must be notified when any changes are made to that asset. 
3. Once a user has subscribed to an asset, they must be able to unsubscribe from that asset. 

Testing Scenarios

Acceptance Criteria	Testing Scenarios	Test Strategy	Covered by frontend test? (Yes/No)	Covered by backend test? (Yes/No)
A subscribe button must be included in the Info Panel of the Content Dashboard for Web Contents.	Given a Web Content When the user opens asset's Info Panel at Content Dashboard Then a subscribe button must be included in the Info Panel	High	yes	no
	Given a others assets types When the user opens assets Info Panel at Content Dashboard Then a subscribe button must be not included in the Info Panel	Low	yes	no
Once a user has subscribed to an asset, they must be notified when any changes are made to that asset.	Given a Web Content When the user has subscribed to an asset Then must be notified when any changes are made to that asset.	Low	no	no
Once a user has subscribed to an asset, they must be able to unsubscribe from that asset.	Given a Web Content When the user has subscribed to an asset Then must be able to unsubscribe from that asset.	Low	no	no

Definition of Done (DoD):

• All Acceptance Criteria were passed;
• Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
• Validated by QA, Product Management and Design;
• No critical bug related to Story scope (FP5 or Impedibugs);
• Make sure that all system documentation were updated (if necessary)