Thanks for the description! It all makes sense, and possible to do with the current Structure version.

But how does "Editing Roles" and limiting the editing capabilities fit into that? Which roles should not be able to change the assignee in the Structure? Will they be able to change the assignee if they just edit the issue?

Not sure how to answer about Initial Vision - it's much like what you see as a product today. Feel free to ask more specific questions though!

Thanks!
Igor

Hello. thanks for your response.
i'm using green hopper plugin for entire team, but Structure is very (i think) usable for management, stories decomposition and planning. so i want do to do a such:
- manager (or lead) creates a first-level story decomposition (via Structure)
- second-level detalization (via Structure after brief)
- team start to work with issues via Green Hopper, but have ability to create issue decomposition via Structure (decomposition just of their issues)
- team work with green hopper till finish.

Could you please write your Initial Vision of Structure plugin? thanks

Thanks for your idea -- could you please expand a bit?

Would you like some users not being able to change Summary or Assignee? You can currently do that via Permission Schemes and Screens - Structure allows editing only those fields that are on the Edit screen.

Please describe what's the use case and how do you envision the users work with this feature, to have us better understand it.

Thanks!