Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How are biotech or AI research teams using Jira to manage complex machine learning workflows?

Larawinzi
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!
August 5, 2025

Hey everyone,

I’m curious to learn how teams in biotech or AI-focused research environments are leveraging J i r a to manage their machine learning and data science workflows.

Biotech companies (which build AI for precision medicine and immunology) must deal with a lot of complex, cross-functional tasks — data Pre-processing, model training, experimentation, validation, documentation, and deployment — all while complying with regulatory standards.

So my questions are:

  • How do you structure your J i r a boards for such technical workflows?

  • Do you use custom issue types or stick with Epics/Stories/Tasks?

  • Are there any automation rules you’ve found especially useful for AI/ML projects?

  • How do you integrate J i r a with tools like Bit-bucket, Confluence, or ML-flow, if at all?

I’m trying to streamline project management for a small team working on AI-driven research, and would love to hear best practices, templates, or lessons learned.

Thanks in advance! 🚀

1 answer

0 votes
Jehan Bhathena
Community Champion
October 26, 2025

Hi @Larawinzi 

Yours seems like a pretty specific use case, I'll try to respond to below:

  • How do you structure your J i r a boards for such technical workflows?

    • Boards are a view into your Jira ticket, they don't need to mimic you workflow, they are instead a good way to get a quick view/update on where the ticket is in the overall process. Eg, you can have just 3 columns in a board To-Do, In Progress and Done, if that give you a better view or you can break it down into stages based on your profession to identify where the ticket currently is
  • Do you use custom issue types or stick with Epics/Stories/Tasks?

    • Out of the box issues types are better when you're following traditional software development, but you can always create more if there is a use case that calls for it. Note, you don't want to over do this since it would add to additional administration, so be mindful when you want to create a new issue type
  • Are there any automation rules you’ve found especially useful for AI/ML projects?

    • Jira automation is very powerful, I personally use it a lot for my day to day workflows, and it can be used to take care of repetitive tasks, if you have a use case, perhaps you can share that and we can help if that would work?
  • How do you integrate J i r a with tools like Bit-bucketConfluence, or ML-flow, if at all?

    • Not sure for ML-Flow, but Bitbucket and confluence have native integrations with JIra

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events