Can a Feature be treated as a task/issue by itself?

[Raghavan alias Saravanan Muthu]

I am using JIRA with an Iterative Type Scheme with Features and Sub tasks to break down the development tasks under one big scope of work (feature). 

I create the sub tasks in such a way that each sub task is an individual / atomic piece of work and can be tested in entirety.

Till now, I have created feature in  such a way that all the sub tasks are the actual tasks and feature by itself does NOT have any actionable content.  It was still alright for me when the feature had more than 6 to 7 sub tasks.  I had however had dilemma while creating a new feature that has only 2 tasks. Can a feature itself be treated as task where I have the major  portion (or the main /determining task) and I create a sub task for the other supplemental task associated.  However, it would be inconsistent with the other features I had created so far. A bit baffled during the middle  of  journey of creating all JIRA tasks associated with all the required features for a release. 

Appreciate an insight or an expert advice here.