SLA on JIRA Cloud? - jira

Is it possible to add SLA (Service Level Agreement) on JIRA Cloud?
I want to add SLA to each ticket right now I don't find any option on Jira cloud. So I'm looking for add/plugin. I did some research but I don't find any add-ons related to Jira Cloud. Some plugins are available but those plugins cannot support Jira cloud.
I stuck here it would be nice if someone suggests any ideas.
Thanks

If you're using Jira Service Desk, they have built in SLAs.

I suppose that you've already found the answer, as this question is quite old. But maybe someone else will look for the solution like this.
So, the answer is yes. You can install plugins for Jira (you can easily find them on Atlassian Marketplace). Among the plugins I would recommend trying is SLA Time and Report for Jira. This add-on can be used for Jira Cloud, Jira Core, Jira Service Management. And it has wide functionality and is easy-to-use. You can find it here.
Hope this will be helpful for someone :)

Related

Automatically create a JIRA ticket from a Template

I need to create a form/template that has all the required fields and that will auto generate a Jira ticket. Is it possible to do something like this in Jira/Confluence?
I think your question would be better suited at an atlassian community forum rather than stackoverflow, as similar questions have been asked over there e.g. here and here.
However, to answer your question, I did a quick search and I think this plugin might be your answer if you have a confluence server instance: Issue Forms for Confluence

Is there an Umbraco plugin to give CRM-type capabilities?

In looking at the Kentico documentation for account and contact management, it seems to give us the ability to create a hierarchy for accounts, such as Account (Client) / Organizational Unit (store locations) / Contact (person at location).
I am looking for a way to accomplish this in Umbraco. We would also want to add multiple fields to the Contact, as they may exist in multiple organizational units.
Is it possible to accomplish this with Umbraco, and if so, how?
There is a free and open-source (according to the latest update from the creator: https://twitter.com/theotron/status/784372313773006849) plugin called Pipeline CRM: https://www.pipelinecrm.co.uk. Source code and installation details are also available on Github: https://github.com/theotron/PipelineCRM.
There's also uSightly, which integrates with Insightly:
https://our.umbraco.org/projects/collaboration/usightly/
I've not used either personally, so I don't know if they would meet your requirements. You can also integrate with other CRM systems yourself if you wish, I know of developers who've integrated with CRMs like Salesforce and Dynamics from Umbraco.
Hope that helps!

Can a single company really not use QB API?...Semi Rant

We need to integrate our custom in house applications with quickbooks. When I saw the QB REST API and the IPP I was like "Yay!!! Finally Qb offered us something useful!".
It was a happy moment.....
Then I read this in the FAQ
I want to integrate my custom (non-SaaS, single-tenant) solution with QuickBooks API. Can I do this?
Not today, but we are considering it.
What? Why?
were paying customers, we have integration problems....largely caused by YOU intuit!
You already built it...I assume it works...so there's no effort whatsoever on your part!
So now you offer an API on a silver platter....but...oh wait....you can't use it.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Somebody tell me that I'm simply misunderstanding this....
Your understanding is correct. IPP Intuit Anywhere is the new platform only for SaaS applications.
Intuit still provides the traditional QBSDK SDK v12, which is useful if you are creating a custom integration for one company, or focused entirely on desktop scenarios only.
QBSDK Ref - https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits/0250_qb
I'm not sure if this is a good option for you but we have created a pretty slick sync with QuickBooks using the SDK for the Method Integration platform. You can use our API with the sync engine to do what you need. You'll need a Method account though which is $40.00 per month.
I have done a lot of integration with QB, and prefer to use the RSSBus ADO.NET provider. It is infinitely easier than using Intuit's SDK, and has great documentation, such as - http://cdn.rssbus.com/help/RQ4/ado/pg_desktoptable-purchaseorders.htm. It works with the Desktop version and QB online.
I am not affiliated with them at all, just a happy customer!

grails payment plugin that is actively maintained and working

I am looking to integrate any actively maintained and working payment plugin with my grails application.
Can anyone who has been through this before give some guidance.
My application need is simple: I need various subscription levels(monthly/annual) and I need to be able to retrieve the payment details.
Any help is appreciated
Bala
Bobby Warner just released the Grails Stripe plugin recently. I haven't used it personally, but I've heard very good things about Stripe's usability, and I know that Bobby is an active, helpful developer who would likely be very responsive to feature requests, feedback, and pull requests.

Jira Conventions and Best-Practices

I have been using Jira since 6months but haven;t been through any document related to various options available and how to use them for maximum output.
There must be some conventions that help in better tracking of the issue.
For instance, Logging work, Linking issues, creating sub-tasks.
It would be of help if you can share some of the features (and the conventions) that you follow while using Jira. It may vary from team-to-team but there must be some generic rules which can be followed.
Any feedback would be of help. Thanks.
Some of our conventions for using JIRA:
Each project has its own JIRA project.
We use the Greenhopper plugin for Scrum planning.
There is no development without a JIRA issue assigned. If needed, Developer add issues on their own.
Commits contain the JIRA ID (for FishEye integration).
Language of JIRA comments.
When working on an issue, it's state is changed to "in progress"
Findings, Problems, Things Done are documented as comments.
Related answer here.

Resources