Hey folks! I’m in a bit of a pickle. Our company just switched to Jira from Asana and I’m struggling to figure out how to organize my event management stuff in the new system.
In my old Asana setup, I had columns for Category, Sub Category, and Tasks. Now I’m trying to find similar options in Jira, but it’s not quite clicking.
I’m thinking maybe the Summary field in Jira could work for my Tasks, but I’m stumped on where to put Category and Sub Category info. Any ideas on how to make this work in Jira?
Here’s the kicker - I can’t even peek at my old Asana setup anymore. My team wants me to turn my Excel template into something Jira-friendly. So I’m basically starting from scratch with my column headers.
Anyone dealt with something like this before? I’d love some tips on how to make my event management workflow smooth in Jira. Thanks!
I’ve worked with both Asana and Jira, and the transition can be tricky. For your event management setup, consider using Jira’s issue types to represent your categories. You can create custom issue types like ‘Event Category’ and ‘Event Sub-Category’. Then, use the ‘Parent Link’ feature to establish relationships between these issue types and your tasks. This approach allows for a hierarchical structure similar to what you had in Asana. For tasks, create a separate issue type and link them to the appropriate sub-category. This method provides a clean, organized view of your event management structure and allows for easy tracking and reporting. It might take some initial setup, but it’ll streamline your workflow in the long run.
hey claire, been there! jira’s a beast at first. for categories, try using labels or custom fields. you can set up a dropdown for main categories and another for subcategories. then use the summary field for tasks like you said. it’ll take some fiddling but you’ll get it! good luck with the switch 
Having transitioned between project management tools myself, I understand your frustration, Claire. In Jira, you can replicate your Asana setup using a combination of built-in and custom fields. For Categories, consider utilizing Jira’s ‘Components’ feature. It’s designed for high-level categorization and can be easily filtered and reported on. For Sub-Categories, creating a custom field with a dropdown list would work well. This allows for consistent data entry and easy sorting. Your Tasks can indeed go into the Summary field, as you’ve correctly surmised. Additionally, look into Jira’s ‘Epic’ feature for grouping related tasks together - it might provide an extra layer of organization that proves useful for event management. Remember, Jira is highly customizable, so don’t be afraid to experiment with different configurations until you find what works best for your workflow.