Filter issues in a Structure by how it was added -- insert automation, extend or manually added

Mark Hinkle June 30, 2023

Given a Structure board that includes a combination of issues added through insert automation, extend automation and added manually how can one within the same Structure board filter to show or hide issues by how they were added?  For example, how could I create a quick transformation to show only the issues manually added?

The only method I can come up with to achieve this is to clone shadow Structure boards removing the automation and using those to compare against issues in the main Structure.  This may work for a moment in time but the clones would need to be maintained as the main board changes over time.  This method is not sustainable.

How could I accomplish this within only one Structure board?

1 answer

1 accepted

0 votes
Answer accepted
Stepan Kholodov _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 30, 2023

Hello @Mark Hinkle 

There is no such tracking in Structure - issues both added manually and automatically are not differentiated. Removing the structure's generators - you can copy them first and then just paste them back to the structure - should indeed help to find out all issues that were added manually since they all automatically added issues will disappear.

If you need to compare two similar structures, you can also use the Double Grid mode and open structures in both left and right panels. The Hide/Show button in the top-right corner in the right panel enables filtering in the right panel that removes all issues that are already present in the right panel. So if, for example, you open the main structure in the left panel and open the second structure where you need to find manually added issues in the right panel, then with this filtering you will only see issues in the left panel that are not present in the main structure.

I hope this helps. If you need further assistance with anything, please reach out to us directly through our portal: https://tempo-io.atlassian.net/servicedesk/customer/portal/6/group/1051

Best regards,
Stepan Kholodov
Tempo

Mark Hinkle June 30, 2023

Thanks, @Stepan Kholodov _Tempo_ .  That's unfortunate.  When removing issues from a Structure it does prevent removal of issues added through insert or extend automation but allows manually added items to be removed.  It would be helpful to surface that attribute for end users.

The workarounds you provided are not always feasible for novice users to perform when working with complex Structures.

Thanks for your help.

Mark

Like Stepan Kholodov _Tempo_ likes this
Guy LaRochelle July 4, 2023

I don't think Stepan's answer is totally right as Structure does show a little "hand" symbol on the left when items have been added manually.

So there should be a way to display only those items that have this "hand".

Stepan Kholodov _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 4, 2023

@Guy LaRochelle 
The hand icon is only displayed for issues that are manually adjusted - if an issue is first added to a structure by a generator, and then a user moved it to a different place in the structure, breaking the rules of existing generators. It's a specific icon that appears in a specific scenario when both Automation and Manual Adjustment features are used.

When an issue is simply added to the structure manually, no icon is displayed and there is no tracking of the difference between added manually or automatically.

Best regards,
Stepan Kholodov
Tempo

Like Guy LaRochelle likes this
Guy LaRochelle July 4, 2023

Thank you for the precision! I stand corrected.

Then I offer that there should definitely be an easy way to filter out the manually added items. Like the "Notes" fields on any Structure, you should add some flag for manually added items, and then allow filtering on that attribute.

Thanks!

Stepan Kholodov _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 4, 2023

Thank you for the feedback, we do have that feature in our backlog already. When there is any news about its release, we will post an update here.

Best regards,
Stepan Kholodov
Tempo

Like Guy LaRochelle likes this
Sara Brander
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 12, 2023

is this feature available already?

Mark Hinkle September 12, 2023

@Sara Brander , no.  There is no way within one structure board to identify or filter the set of issues based on the method the issue was added.

Sara Brander
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 12, 2023

there is no way to filter the structure by the added notes field?

Mark Hinkle September 12, 2023

There's no apparent way using the additional Notes fields aside from entering some keyword manually in as a note on each item and filtering based on that value.    My original question is for a mechanism to identify the method an issue was added to a structure without having to manually tag each issue. 

@Stepan Kholodov _Tempo_ , any additional insights on the latest releases?

Stepan Kholodov _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 25, 2023

@Mark Hinkle 

At this time, there is no mechanism in Structure for tracking how an issue is added - manually or automatically. We will also notify you here when the mentioned feature is released.

Best regards,
Stepan Kholodov
Tempo

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events