Use of projects vs components for small solutions within a platform

Our organization recently adopted SharePoint and our team is tasked with maintaining the platform itself but also to develop solutions using SharePoint. 

I initially set up JIRA so that the SharePoint product is one project and all solutions we develop are their own respective projects. I created a category called SharePoint so I could report across all our initiatives. 

We have one scrum team to perform all the work, so I created a scrum board for the SharePoint category as opposed to one per project. This way, we see everything we need to do in one place and our platform owner can prioritize our work for us. 

The challenge we are facing is versioning. At the end of our sprint, we deploy a package. Custom code, content, configuration files. We would like to version that package but versions are not associated to categories. 

Should we just have one giant project and use components to list all the solutions built in it? 

What are the best practices for platform projects like this?

1 answer

I suggest using the native functionality of JIRA Projects to take advantage of "Versioning", so I agree with your own suggestion. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

222 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you