JIRA upgrade from 4.0.x to JIRA 5.1.3 - will the same running license work?
Jira licence includes 12 months of maintenance (updates/support) , during that time you can update for free without purchasing a new licence. After those 12 months you can use your Jira freely, but you cannot upgrade it. To learn more have a look at the Jira's licensing information.
A JIRA commercial/academic license entitles you to: (as for Jira 5.0)
Deploy a single instance of JIRA in a production environment on 1 server
Unlimited projects and issues
Perpetual JIRA use
Software maintenance for 12 months - including all updates and online support (from Sydney, Australia and San Francisco, USA during local business hours)
Full source code (under a developer source license which allows for broad customization)
Licensing fees are quoted per number of 'active users'. An active user in JIRA is by definition any user account in the system with the "JIRA Users" global permission, i.e. anyone who can log in. Unlimited 'anonymous users' are permitted on all licenses.
Related
I`m trying to understand the licensing of MSDN. If I just want to perform check in/out , see History and similar operations as a member of a TFS Team of Developers Do I need an MSDN license ?
Thank you very much
To license TFS server , you’ll need a TFS server license and a
Windows operating system license (Windows Server is best) for each
machine running TFS, plus a client access license for each person
connecting to TFS. Client access licenses (CALs) aren’t required for
people who just access work items – assign them “Stakeholder” access,
which is free.
Extensions to TFS such as Test Manager, Package Management, and
Private Pipelines require an additional purchase. Some TFS Extensions
are included with Visual Studio Enterprise subscriptions and many
others are free. Paid extensions can also be purchased monthly, no
Visual Studio subscription is required.
In your case, if you want users to check in/out, view source control history, you still need a CAL. Which means you still need a MSDN subscription to handle this. Unless, people who just access work items – simply assign them “Stakeholder” access, which is free.
Unlike the Classic Purchasing above, if you don't want to buy a MSDN subscription.
Suggest you to use Modern Purchasing.
The most advantage: No need to make a 3-year purchasing commitment for
TFS—you can pay month-to-month and cancel any time. For example: Buy
VSTS for TFS CALs. When you buy VSTS users (starting at $6/month),
those same users have a TFS CAL and can connect to any TFS in your
organization. If those users also need TFS extensions like Test
Manager or Package Management, or if you need additional Private
Pipelines for your team, you can purchase these through the Visual
Studio Marketplace. All VSTS charges are month-to-month. See detailed
instructions.
For more info you could take a look at this official doc: Team Foundation Server Pricing
Besides, If you want to double confirm this and know more information about TFS license, you could call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations: http://www.microsoft.com/licensing/
Does a local TFS license cost the same as a VSTS on Azure? What will be the best licensing option to have TFS on-premise?
No, there are not the same.
To license TFS on-premise server, you’ll need a TFS server license and a
Windows operating system license (Windows Server is best) for each
machine running TFS, plus a client access license for each person
connecting to TFS. Client access licenses (CALs) aren’t required for
people who just access work items – assign them “Stakeholder” access,
which is free.
Extensions to TFS such as Test Manager, Package Management, and
Private Pipelines require an additional purchase. Some TFS Extensions
are included with Visual Studio Enterprise subscriptions and many
others are free. Paid extensions can also be purchased monthly, no
Visual Studio subscription is required.
TFS server costs $499 and includes 5 TFS CALs. Additional TFS CALs are $499 each.
Unlike the Classic Purchasing above, suggest you to use Modern Purchasing. The most advantage: No need to make a 3-year purchasing commitment for TFS—you can pay month-to-month and cancel any time. For example:
Buy VSTS for TFS CALs. When you buy VSTS users (starting at $6/month), those same users have a TFS CAL and can connect to any TFS in your organization. If those users also need TFS extensions
like Test Manager or Package Management, or if you need additional
Private Pipelines for your team, you can purchase these through the
Visual Studio Marketplace. All VSTS charges are month-to-month. See
detailed instructions.
For more info you could take a look at this official doc: Team Foundation Server Pricing
Besides, If you want to double confirm this and know more information about TFS license, you could call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations: http://www.microsoft.com/licensing/
I was looking around for some time, but couldn' t find a free add-on to manage test cases, test plans et scenarios ect.
Do you know any who is free that can be installed on a Jira cloud solution ? or should i create my own custom Jira project for it, if there is no free one
Thanks
You could try the TestFLO app - it's available for both Server and Cloud instances of Jira. Not fully free, but at least you've got a free trial :) You can find it on Atlassian Marketplace, just like any app for Jira.
We are going to work together with another company which using TFS/Octopus Deploy.
The item is currently in phase one, which includes building the platform and ensuring that all components work together cohesively.
I'm confused with the license required with TFS. It's easy to understand the license for TFS server. However, there seems to be a client license for each client, why we need two license for a product? And what's the association with TFS client license / VS or MSDN subscription?
TFS is licensed on a Server/CAL model. Thus, you need 1 Server license for the TFS server and 1 TFS CAL (client access license) for each user that will use TFS features.
That TFS CAL covers the usage no matter how the user accesses TFS (i.e. Visual Studio, Eclipse, Web Access client, Excel, MSProject, 3rd party tool, ect, etc).
The two ways to acquire TFS CALs are:
Purchase a TFS User CAL
1 TFS CAL (and 1 TFS Server license) is included in each Visual
Studio/MSDN subscription. Thus, anyone who has an active MSDN
subscription assigned to them is covered with a TFS CAL.
Client access licenses (CALs) aren’t required for people who just
access work items – assign them “Stakeholder” access, which is
free.
Extensions to TFS such as Test Manager, Package Management,
and Private Pipelines require an additional purchase. Some TFS
Extensions are included with Visual Studio Enterprise subscriptions
and many others are free. Paid extensions can also be purchased
monthly, no Visual Studio subscription is required.
More details please refer below two blogs:
Understand TFS Licensing
Team Foundation Server 2017 Licensing
As you have already stated you need a license for TFS itself, but if you have a single Visual Studio subscription this is included.
Clients connecting to TFS might need a license depending on the access level needed. A lot of the planning features are free (stakeholder level) whereas source code and more advanced features will require either a Basic (most features except Test) or Enterprise (all features) level access.
Basic level can be obtained by either buying it directly through VSTS or by buying a product that includes a CAL license e.g. Visual Studio subscription.
For smaller teams, you can use TFS/VSTS for free but with a maximum of 5 users.
You can read more on the Team Foundation Server pricing page.
My organization serves the application development needs a number of different companies. When we develop an application for a company, we typically have users from that company perform the testing.
If we were to use TFS Web Access for testing, are we able to transfer the CAL license from one company's tester to another once a project has been completed? I couldn't find anything about it in their licensing whitepaper.
From the TFS licensing whitepaper:
if the contractor is using the client’s Team Foundation Server then
the client must supply a Team Foundation Server CAL for the
contractor’s use. This could be a CAL purchased separately or a CAL
that is included with the MSDN subscription that the client assigns to
the contractor temporarily.
So yes, it appears you can transfer CALS to different users as long as only one user is using the CAL (accessing the server) over any given period. (I think a "user" is not locked down to a specific individual)
However, this:
Team Foundation Server CALs are only valid for accessing a Team
Foundation Server acquired by the same organization
...implies that your customers cannot use your CALs, so would have to purchase their own.
It may be possible (from my reading of the white paper) for you to get a Device CAL, assign it to a laptop, and lend the laptop to your customer. But it'd be best to ask Microsoft to confirm that.
However, if your customers are only using the web interface for test feedback (limited to basic work item operations such as reporting bugs, responding to feedback requests, and viewing reports) they will not require a CAL. Clearly Microsoft recognises that your customers will need to be able to interact with your server to report bugs and feedback.
But ultimately if you're not sure, ask Microsoft to give you a clear (and legally watertight) answer. You can read the licensing documents until you lose the will to live (or even more than 3.2 minutes if you must), or ask a thousand of us to post our interpretations, but you won't know for sure unless you get MS to provide the actual answer.