Claris FileMaker vs. Jira Service Management

If your company is really small, I can understand the need for a product like this. However, I would go for MS Access... FileMaker Pro can not be integrated with other systems (like MS Access can at least be handled by C# for instance, and can be integrated with MS Excel or even SQL server). I'm really not sure in what scenario one would choose for FileMaker Pro. If your application or company grows bigger, you're going to have a problem to move to another environment. Also, the fact that only one person can work with the backend at any given time is a problem in a somewhat larger company.

Incentivized

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

• The relational database management system makes the program highly customizable to fit the needs of any product. You can add a ton of information to each record and update your inventory on a regular basis with an Excel import or manually inside of the record. It has the capability to incorporate barcoding, which can manage your available inventory with ease.
• The scripting language allows FileMaker to automatically calculate complex algorithms automatically or generate report outs with the click of a button. This allows for greater UI, especially with active users who are not familiar with writing code. Almost all of our internal data is linked to the FileMaker database
• The server license allows many users to update the database in real time, which is handy if your inventory is constantly changing. We have users with Macs, PCs, iPhones and handheld tablets linked to our FileMaker database and they are updating the information constantly throughout the day.
• If you invest some time into formatting and scripting the database, there is a high ease of use for users without knowledge of any programming or FileMaker itself.

Incentivized

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• Developer features need to be beefed up - namely adding the ability to search code for a phrase or keyword and the ability to do the same in the "relationship graph" in the database.
• Add ability for users to edit the same table record at the same time by version control.
• Allow Filemaker Server to use more than 1 core; currently multi-processing is not supported and it can be tricky to find just the right server to support the application you've built to the fullest capacity.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

It it not really up to me but my opinion does have some weight in the decision and the reason I would renew my use FileMaker Pro 8.5 is because I am finally getting used to it! Now that I have been working with the program, tasks have become quicker and projects are getting done faster. File Maker Pro 8.5 really is a versatile tool and I think we are just scratching the surface with it's abilities.

Incentivized

It's almost what it should be after so may years and with Apple's longevity and strength behind it. For people who earn their living based on efficiency I think there are too many developer obstacles that waste time and therefore money.

Incentivized

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

Incentivized

mostly never issues and if there are they are resolved fast

Incentivized

for the most part but lots of error messages if you type something h correctly

Incentivized

The forums are great with lots of helpful experts and the staff monitor them to provide help where needed. There have been a couple of unique technical issues I've had to deal with that I haven't been able to get resolved so I chose to score this a 9 instead of a 10.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

easy to follow along and was able to jump in right away

Incentivized

Suggest you use an iterative R.A.D. or AGILE development approach. (i.e. rather than writing a gigantic spec for a system, then building it). FileMaker facilitates quick prototypes. Developing an example, then allowing users to "try it out" is a snap.

Incentivized

FileMaker is still the quickest way to go from zero to having a minimum viable working solution. Simple solutions can be built in as little as a afternoon of development. It is the only tool I am aware of which allows tech savy end users with domain knowledge to build bespoke apps for their businesses without undertaking professional software development training.

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

it's most definitely does as we are a unique business to use this for scholarship awarding

Incentivized

• We are a more agile company because of FileMaker. A few of us who are tech-savvy enough to manage the database (but are not professional developers) can make needed adjustments to our database without having to employ an in-house developer or contract with a 3rd party. As our business processes evolve and change, it's easy to update the database to accommodate those changes.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized