How to Access Jira Service Desk Data Using Entity Framework

Microsoft Entity Framework serves as an object-relational mapping framework for working with data represented as objects. Although Visual Studio offers the ADO.NET Entity Data Model wizard to automatically generate the Entity Model, this model-first approach may present challenges when your data source undergoes changes or when you require greater control over entity operations. In this article, we will delve into the code-first approach for accessing Jira Service Desk data through the CData ADO.NET Provider, providing you with more flexibility and control.

1. Open Visual Studio and create a new Windows Form Application. This article uses a C# project with .NET 4.5.
2. Run the command 'Install-Package EntityFramework' in the Package Manger Console in Visual Studio to install the latest release of Entity Framework.

3. Modify the App.config file in the project to add a reference to the Jira Service Desk Entity Framework 6 assembly and the connection string.

   You can establish a connection to any Jira Service Desk Cloud account or Server instance.

   Connecting with a Cloud Account

   To connect to a Cloud account, you'll first need to retrieve an APIToken. To generate one, log in to your Atlassian account and navigate to API tokens > Create API token. The generated token will be displayed.

   Supply the following to connect to data:

   • User: Set this to the username of the authenticating user.
   • APIToken: Set this to the API token found previously.

   Connecting with a Service Account

   To authenticate with a service account, you will need to supply the following connection properties:

   • User: Set this to the username of the authenticating user.
   • Password: Set this to the password of the authenticating user.
   • URL: Set this to the URL associated with your JIRA Service Desk endpoint. For example, https://yoursitename.atlassian.net.

   Note: Password has been deprecated for connecting to a Cloud Account and is now used only to connect to a Server Instance.

   Accessing Custom Fields

   By default, the connector only surfaces system fields. To access the custom fields for Issues, set IncludeCustomFields.

   <configuration> ... <connectionStrings> <add name="JiraServiceDeskContext" connectionString="Offline=False;ApiKey=myApiKey;User=MyUser;InitiateOAuth=GETANDREFRESH" providerName="System.Data.CData.JiraServiceDesk" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.JiraServiceDesk" type="System.Data.CData.JiraServiceDesk.JiraServiceDeskProviderServices, System.Data.CData.JiraServiceDesk.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
4. Add a reference to System.Data.CData.JiraServiceDesk.Entities.EF6.dll, located in the lib -> 4.0 subfolder in the installation directory.
5. Build the project at this point to ensure everything is working correctly. Once that's done, you can start coding using Entity Framework.
6. Add a new .cs file to the project and add a class to it. This will be your database context, and it will extend the DbContext class. In the example, this class is named JiraServiceDeskContext. The following code example overrides the OnModelCreating method to make the following changes:
   • Remove PluralizingTableNameConvention from the ModelBuilder Conventions.
   • Remove requests to the MigrationHistory table.
   using System.Data.Entity; using System.Data.Entity.Infrastructure; using System.Data.Entity.ModelConfiguration.Conventions; class JiraServiceDeskContext : DbContext { public JiraServiceDeskContext() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<JiraServiceDeskContext>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
7. Create another .cs file and name it after the Jira Service Desk entity you are retrieving, for example, Requests. In this file, define both the Entity and the Entity Configuration, which will resemble the example below: using System.Data.Entity.ModelConfiguration; using System.ComponentModel.DataAnnotations.Schema; [System.ComponentModel.DataAnnotations.Schema.Table("Requests")] public class Requests { [System.ComponentModel.DataAnnotations.Key] public System.String RequestId { get; set; } public System.String ReporterName { get; set; } }
8. Now that you have created an entity, add the entity to your context class: public DbSet<Requests> Requests { set; get; }
9. With the context and entity finished, you are now ready to query the data in a separate class. For example: JiraServiceDeskContext context = new JiraServiceDeskContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.Requests select line;