Why sometimes issue interface and sometimes issueservice

I'm reading a book that says use IssueService for dealing with issues but I created a customfield and it generated a file that injects an Issue interface

getVelocityParameters(final Issue issuepublic Map<String, Object> getVelocityParameters(final Issue issue,
 final CustomField field,
 final FieldLayoutItem fieldLayoutItem)

I'm wondering why one or the other and which one are you supposed to use?


1 answer

1 accepted

This widget could not be displayed.

Figured it out. I was confusing two different actions here. The Issue is already created using the IssueService and then the instance is passed into this method. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

266 views 1 3
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