Is there a way to put addresses in issues

[Jens.Slofstra]

Hi everyone,

My company sets data for a range of addresses given to us by a client. We use a Kanban board to keep track of the progress of these addresses but not individually. We use the issue hierarchy to group them in sets that have the same data. The issue hierarchy is as follows:

• City (Feature)
• District (Epic)
• Neighborhood (Task)
• Collection of addresses (with the same data to be set) (Sub-task)

In these collections we use the description to set all the addresses belonging in this collection (normally between 10-20, in extreme cases we god 150 addresses).

This process works fine as is but has one big problem. Sometimes new data gets added to each address. This results in a further splitting of the already made collections.

Because of this mistakes are made and addresses are accidently placed in two collections instead of one. This means that we create two datasets for the same address (if not spotted).

To counteract this I was wondering if there is a way to add a specific address (can be a ticket, variable, etc) to a collection. Which in turn prevents another collection from using the same address.

My first idea was to add to the issue hierarchy so that for each address a new issue is made and has a parent that is the collection. Only issue with this is that a project has about 50.000 addresses and I don't know if that is a problem for Jira.

Has anyone any other ideas. Everything is welcomed.
Thanks already,

[Jerrold - Empyra]

Hi 

One potential solution to resolve your concern could involve the implementation of a tagging or labeling system for addresses within Jira. This would enable you to allocate specific tags or labels to each address, thereby indicating its respective collection. By adopting this approach, you can ensure that each address is linked with only one collection.

To implement this strategy:

Create Labels or Tags: Within Jira, establish a series of labels or tags corresponding to each collection. For instance, if your collections are named "Collection A", "Collection B", etc., create labels/tags with matching names.

Assign Labels to Addresses: When adding addresses to collections, assign the relevant label/tag to each address based on its associated collection.

Enforce Single Collection Assignment: Introduce a process or guideline within your team to guarantee that each address is assigned only one label/tag corresponding to its collection.

By utilizing labels or tags, you can uphold the existing structure of your Kanban board without necessitating the creation of additional issues for individual addresses. This method should help prevent duplication of addresses across multiple collections and minimize the likelihood of errors. Moreover, Jira should be capable of efficiently managing a large number of labels/tags, thus accommodating 50,000 addresses without difficulty.

Thank you.

[Jens.Slofstra]

Thanks for the reply, I will look into it.