Say, if an application has both admin console(admin user only) and user consoles(end user) and a course of action in admin console will be reflected in user console. So, even though the goal is considered to be for actual end user, changes will also be seen for admin as well.
We currently have one story with acceptance criteria saying admin user should be able to re-order menu items in admin console.
Here is the sample feature:
Feature: Re-order menu items
In order to change the display order of menu items for end users/customers in user console
As an admin user
I want to re-order menu items in admin console
It makes sense to have single feature to specify the expected behavior(or goal) , but cases like these where feature could be one but outcome is just not at a single place and also the stakeholders are different- what is the better approach - single feature (or) multiple features? Any recommendations?