I believe Task in JIIRA is something that we create to be completed in a sprint

[Mythili Patiballa]

And we will be knowing of what was agreed upon piece of functionality. 

Can we test and close a ticket if it is raised as Task ?

[Nic Brough -Adaptavist-]

Welcome to the community.

You are right, a lot of us do exactly that.  Any issue raised at the level of "Story" (in other words, below Epic but above sub-tasks) is "an agreed upon piece of functionality".  They do not have to be stories - anything at that level should be drawn into sprints.

So, yes, you absolutely can test and close a ticket when raised as a task, or story, or feature, or whatever you want to call things at that level.

[Mythili Patiballa]

Thanks Nic !! 

Can a story be created for Backlog ? I think we usually create features for backlog that can be discussed for later sprints..

But Story -> is like the topic under discussion and we aim  for the current sprint

Task ->  is inside a story level that is already agreed to work upon

Feature  -> backlog that can be taken for later sprints

Epic -> Multi stories includes features that can be broken down for later sprints

Hope my understanding is correct.

[Nic Brough -Adaptavist-]

Yes, stories go in the backlog, but the rest of the post is not quite how Jira works.

Jira has three layers

• Epic - (which is a way of grouping Stories, so you've got that one right)
• Issue - usually a Story, but you can create plenty of other types.  The name of an issue type is just a label.  So you can call them "tasks" or "features" if you want.  The issues at this level are "Stories" though, in Agile terms and how you've described Stories, whatever you happen to call them.  If they are in the backlog, you have not agreed to do them (yet).  If you have put them into a sprint, then you have said you're going to do them.
• Sub-task - these are part of Issues on the layer above, and follow their parent issues/stories - if you agree to do the Story, you're implicitly saying you're going to do all the sub-tasks as well.  Again, the names on these are simple labels - you can use task, feature, technical task, whatever

Note that the names of issue types have to be unique, so you can't have Task and Task on the two levels unless you add something to differentiate them like Task (Story) and Task (Sub-task)