Problem
-------

We're working in a full-stack development team composed of three guilds (backend, frontend, QA), so as a team we share a single sprint board.  

User stories we take into our sprints are written in a way that they may require work from at least one or multiple guilds.

So far the story received single estimation as a composition of votes for all involved guilds. But this way we're unable to tell how heavy the story will be for every single involved guild, which causes us complications in sprint planning meetings and later on in sprints.

Imagine you want to maximize the team effectivity by minimizing down-times of each guild. Because (not every, I know) user story can be worked on in parallel by multiple guilds, you can do that by selecting such stories to sprint where summary of estimations for each guild gives closest capacity of that guild. You mustn't, of course, forget to count with dependencies between stories.

Question
--------

Is it OK for single user story to have estimations for each of involved guilds? And if so, is Jira (cloud) able to deal with that? Does anyone have any personal experience?

Note
----

We also thought about estimating only sub-tasks, not user story itself, but we rejected that because this would inflate the estimation unreasonably.

Imagine single story with work required by all three guilds. In refinement the story receives following estimations (3 SP: backend, 1 SP: frontend, 2 SP: QA). The guilds agree on single estimation of 5 SP and give this to the user story. Sub-tasks for each guild are left unestimated (with estimation zero).

In opposition when the story itself would not receive any estimation (zero), but sub-tasks for each guild would receive their respective estimations. This would give unreasonably higher SP count (here 6 SP instead of 5 SP in the first case), because you'd have to sum all SPs for each sub-task.