Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How we can separate the effort of an idea for cross-functional request

Erfan Alvand April 11, 2023

We are using our internal scoring for each item but for each, we have an ETA in order to calculate the development estimation.

In functional items, there is no challenge and easily we can communicate with teams, But when it comes to cross-functional items we are adding X days which it's a sum up of effort from different teams.

The question is, How we can separate them in order to manage it easier when we are planning for a quarter we will see only effort and development estimations related to a function in a cross-functional project.

Screen Shot 2023-04-11 at 5.21.42 PM.png


1 answer

Suggest an answer

Log in or Sign up to answer
2 votes
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 12, 2023

Hi Erfan, 

I would first suggest to create a new select field, called Category (for example) and give it two options. 

Then you classify each idea under this category. 

Screenshot 2023-04-12 at 11.27.08.png

From there you have two ways to separate them: 

Within a view: 

Create a group based on this field 

Screenshot 2023-04-12 at 11.27.31.png

In separate views: 

Create a view with a filter on one option, and another view, with a filter on the other option; 

Screenshot 2023-04-12 at 11.28.29.png



Erfan Alvand April 17, 2023

Thanks for your reply @Hermance NDounga

Actually, already have this X-Functional and Functional but let me elaborate on the problem:

We have "Project A" there will be 4 teams will be involved.

Team 1 -> 5 Days Effort

Team 2 -> 3 Days Effort

Team 3 -> 3 Days Effort

Team 4 -> 3 Days Effort


Right now if we wanna manage it should be 5 columns, 4 for each team and one to sum up all days. But imagine the team wanna update it and we need to do everything manually, Sum up the total, and update...

Also consider there is only 4 functions and it will be a little make sense to have 5 columns but the problem is we have more than 4 functions in our company and in this case we need to have a lot of columns for team and it will not be manageable easily and also will have a bad look when we will have +10 columns for our teams...

Like Steffen Opel _Utoolity_ likes this
AUG Leaders

Atlassian Community Events