Is there any advantage of using Story instead of custom issue type ?

[Nivedita R]

I am setting up the project for my Programme Management team. We deal with Projects. So instead of Story and Task, I am thinking of introducing custom issue type called Project. I might consider including one more called "Operational Activity". Are there any disadvantages in not using the standard issue types like Story and Task ? Would plugins support such custom issue types? Is there any benefit of using Story and Task over custom issue types?  We intend to use Portfolio for Jira tool. We would have Epics and Initiative as a level higher than Epics. Would Portfolio work fine with custom issue types? 

[Hernan Halabi - Elite IT Consulting Group · Accepted solution]

Hello @Nivedita R welcome to the community. There is no problem to use your own custom fields instead of tasks and stories. It would be different if you would be considering replacing epics. You just need to make sure that the story points custom field has a valid context for the new issue types in case you are using it.

[Nivedita R]

Thanks for the prompt reply.  @Hernan Halabi - Elite IT Consulting Group Yes. We intend to use Story Points. I understand that we will have to set the context for the Story Points field and include it in the screens related to these new custom issue types. If this is done, then we are good to replace the standard Jira issue types like Story and Task with custom Issue Types. Thanks !  
PS: Sorry, I meant to put this as a reply to your comment. By mistake, I added this one as a separate reply. I do not see any option to delete this note.

[Hernan Halabi - Elite IT Consulting Group]

No worries, your concern was solved, that's the goal here anyway