Durpal Content types vs Jira Issue types

I love meeting clients and listening to their problems. I remember working for client understanding their requirements I used to start visualising the structure of the solution. When I was working for creating a web application I used to start asking question to myself. Should I create a new Content type for this or use taxonomy instead for similar type of content. There are number of factors to consider here. Especially the fields that are required on the Content type.

In Drupal you have Content type, Jira has Issue type and quite often I ask myself same question. Should I create a new Issue type for this type of ticket or use an existing one along with Components.

In Drupal you have the option to display what fields will appear on edit form and what fields needs to be displayed. In Jira as well there are three operations - Create, Edit and View. One thing which I miss in Jira is the ability to have different types of views. In Drupal you have Full, teaser, RSS and few other types of displays.

I don't even know why I am doing this comparison. They are tools for different purposes but sometimes it is good to learn from tools in other domains. Drupal being an open source is a product of thousands of contributors and the way it has evolved is amazing.

Want to contact me?

Life begins outside your comfort zone and that is where your courage is developed". Write to me by filling this form. For living I am an Atlassian Consultant who love both Jira and Drupal. I am the author of "Mastering JIRA" and "Mastering JIRA 7" books. I Love both JIRA and Drupal (a bit more). You can Write To Me and I will get back to you as soon as I can. Have a nice day!

Social Links

Subscribe to my mailing list.

Enter your email address: