Skip to main content

End User License Agreement

IMPORTANT – READ CAREFULLY: The END USER LICENSE AGREEMENT (hereinafter referred to as EULA) is a legal agreement between you (either an individual or a single entity) and howtojira (hereinafter referred to as howtojira) for the Atlassian Add-on (hereinafter referred to as SOFTWARE). By installing, copying, or otherwise using the SOFTWARE, you agree to be bound by the terms of this EULA.

This EULA is to be read in conjunction with "Atlassian Marketplace Terms of Use" available at http://www.atlassian.com/licensing/marketplace/termsofuse . In case of any conflict between the terms of this License and Atlassian Marketplace Terms of Use, the former shall prevail.

1.Grant of License

  1. The SOFTWARE is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties.
  2. This license grants you the limited, worldwide, non-exclusive to install and use the SOFTWARE for the number of licensed users.
  3. You are allowed to copy the software for backup, archival as well as testing purposes.
  4. You may not sell, transfer or convey the Software to any third party without howtojira’ prior express written consent.

2. Ownership and Reservation of Rights

  1. All rights of any kind, which are not expressly granted by the present EULA, are entirely and exclusively reserved to and by howtojira.
  2. The Software is licensed, not sold. You do not acquire any ownership rights as a result of downloading, installing or using the SOFTWARE.

3. Termination

  1. You may terminate this EULA at any time by destroying all your copies of the Software.
  2. The license will automatically terminate if you fail to comply with the terms of this agreement.
  3. On termination, you are required to remove the SOFTWARE from your computer and destroy all copies of the Software and Documentation and all its component parts.
  4. There shall be no refund or adjustment for amounts paid by you to howtojira.
  5. The provisions of the present EULA which by their nature extend beyond the termination date of the EULA will survive and remain in effect and enforceable until all obligations are fully satisfied.

4. Infringement Indemnification

  1. howtojira will hold YOU harmless, defend and indemnify You, against a third party claim to the extent based on an allegation that the SOFTWARE infringes a third party intellectual property right, provided that howtojira: (a) is promptly notified and furnished a copy of such Claim, and all other documents that the claim is based on (b) is given reasonable assistance in and sole control of the defense thereof and all negotiations for its settlement.
  2. If the SOFTWARE becomes, or in the opinion of howtojira may become, the subject of a Claim, howtojira may, at its option and in its discretion: (a) procure for YOU the right to use the SOFTWARE, free of any liability; (b) replace or modify the SOFTWARE to make it non-infringing; or (c) terminate your right to continue using the SOFTWARE and refund, in this case, any license fees related to the SOFTWARE paid by YOU.

5. Limitation of Liability

  1. Except for the indemnification clause, neither party will be liable to any person for the use of the SOFTWARE.
  2. In no event will the total liability under any claims arising out of this agreement exceed the license fees paid under this agreement.

6. Publicity Rights

  1. howtojira has the right to use your name for commercial purposes and/or to include your name and/or logos in their clients list or any promotional materials.
  2. You can deny this right at any time by submitting a written request via email to support@howtojira.atlassian.net , requesting for exclusion from subsequent promotional materials.
  3. howtojira will remove the name and/or logos from existing promotional materials within their best effort.
  4. Requests submitted after purchasing may take thirty (30) calendar days to process

7. Entire Agreement

  1. This EULA represents the complete agreement concerning this license between the parties and supersedes all prior agreements and representations between them
  2. howtojira may amend or modify this EULA from time to time. Users can request to be informed of any changes by submitting a written request via email to support@howtojira.atlassian.net
  3. Unless required by Laws, we agree not to make modifications that would substantially diminish our obligations during your then-current License Term
  4. For our free software, you must accept the modifications to continue using the software. If you object to the modifications, your exclusive remedy is to stop using the free software
  5. For our paid software, customers can raise their objection by providing notice to support@howtojira.atlassian.net within thirty (30) days of us providing notice of the modification
    If the resolution is unacceptable, customer can request for termination and refund for any fees pre-paid for use of the affected Software for the terminated portion of the License Term
  6. For avoidance of doubt, any Order is subjected to the version of the version of Agreement in effect at the time of the Order
  7. If any provision of this EULA is held to be unenforceable for any reason, such provision shall be reformed only to the extent necessary to make it enforceable and the remaining provisions of this EULA shall remain in full force and effect.This EULA represents the complete agreement concerning this license between the parties and supersedes all prior agreements and representations between them.


Email: support@howtojira.atlassian.net

Comments

Post a Comment

Popular posts from this blog

How to export a list of Jira custom fields to csv (Jira Data Center)

 Hello All ! As a Jira administrator it is very important to keep an eye on the number of custom fields you have in your instance because the number of custom fields directly impact your instance performance. Atlassian also has confirmed this in their documentation .  One of the important strategies to keep your custom field number low is to reuse them as much as possible across projects. When you get a request from a user to create a custom project, you can provide a list of custom fields upfront, and ask the user to choose existing fields instead of creating new ones. Out of the box, Jira doesn't provide an easy way to export the custom field list to a csv file to share with non Jira admin users. In this blog I will share how I exported all Jira custom fields into a csv file using Jira REST API and Python. This solution was tested on Jira Data Center version 8.x, Python3 and Windows 11. Let's see how we can get the custom field list in 3 easy steps. Note : I assume that you
Post a Comment
Read more

How to send a survey with multiple questions in Jira Service Management (Jira Cloud & Jira Data Center)

Hello All, Out of the box Jira Service Management only allows to add one question for the customer satisfaction (CSAT) survey once a ticket is resolved. But most teams like to collect feedback on different aspects of the support provided to the customer by adding more than one question. In this blog I will go over a workaround to send multiple questions to the customer when a ticket is resolved.  Scenario Support team uses Jira Service Management to work on customer requests. Once a request is resolved an email needs to be sent to the customer with a survey including multiple questions. Survey response needs to be tied to the Jira ticket number. Solution In order to send multiple questions we will use a google form.  When the ticket is resolved the reporter will get an email with a link to a google form containing the survey questions.  The first field of the google form will contain (this will be autofilled) the issue key where the user received the survey. Given that we are not using
Post a Comment
Read more

How to setup Jira SLAs for global teams across multiple time zones (Jira Cloud & Jira Data Center)

Hello All! Being a global company creates the need to have IT teams across different parts of the world in different time zones. When you have team members working in different time zones you also need the ability track SLAs for the work they do. In this blog I will go over a solution to track Jira request SLAs for global teams across multiple time zones. Scenario: IT department have three teams in three different time zones (Barcelona, New York,  Los Angeles).  Employee requests are processed by the IT team assigned to the location of the employee. All three IT teams work from 9:00 AM to 5:00 PM (Monday - Friday) in their respective time zones.  Every request submitted to IT needs to be resolved within 40 business hours.  Requests can be transferred to another team and the SLA clock should be updated to use the respective time zone of the teams location.  Office Location Timezone Hours (M-F) Time to resolution Barcelona CET 9:00 AM - 5:00 PM 40h New York EST 9:00 AM - 5:00 PM 40h Los
Post a Comment
Read more