Service API Placeholder
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	• Trellimport
	Feb 27 2015, 1:15 AM

Description

My gut is to put the service requirements in each story as part of the acceptance criteria. Does that jive?

Trello card: mZbeMdyK

column: Should have

Event Timeline

• Trellimport added a project: Gather.Feb 27 2015, 1:15 AM

• Trellimport added a subscriber: • JKatzWMF.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 27 2015, 1:15 AM

• JKatzWMF moved this task from Needs triage to Sub tasks on the Gather board.Feb 27 2015, 6:23 PM

I agree that there should always be a mentioning if the backend (api) needs to change to support a given feature. That said, why is this a task? I don't think we can act on it - simply make it a rule of task creation.

Jdlrobson moved this task from Sub tasks to Developer backlog on the Gather board.Apr 3 2015, 9:00 PM

• KLans_WMF triaged this task as Low priority.Sep 16 2015, 5:16 PM

MBinder_WMF added a project: Web-Team-Backlog.Apr 27 2016, 4:26 PM

This task was declined as part of a batch-decline related to sunsetting the Gather project. Please ping (politely) if this task should be reopened. For more information, you can also see here: https://www.mediawiki.org/wiki/Extension:Gather

MBinder_WMF unsubscribed.Jun 2 2016, 11:12 PM

Service API PlaceholderClosed, DeclinedPublicActions

Description

Event Timeline

Service API Placeholder
Closed, DeclinedPublic
Actions