The first problem I ran into is that the Atlassian.NET SDK doesn’t support querying sprints directly. Var jira = Jira.CreateRestClient(jiraServer, username, password) Public static Jira Create(string username, string password, string jiraServer) I’m guessing their LINQ provider supports paging via Skip and Take but since I was only querying a few items in a given sprint, I didn’t feel the need for paging code. I also needed to set MaxIssuesPerRequest when creating the client as it’s pretty low by default (20 or so IIRC). The only additional difference is I later stored the JIRA URL there as well previously that was stored in App.config. I won’t repeat those details here since they were in my last post, Console App Credentials and the Windows Credential Manager. Those I read from the Windows Credential Manager, prompting for if missing. There was a bit more flexibility going directly to JIRA’s REST API but since this was a quick utility I didn’t want to deal with creating a REST client, authentication and the like.Ĭreating a JIRA rest client required a server URL, username and password. I decided to use the Atlassian.Net SDK via NuGet. I really dislike tedious, repetitive tasks so I probably end up writing too many utility apps / scripts but why stop now? I thought I’d research what JIRA offered API wise and see if I could throw together a console app that queried issues in the current sprint and wrote detail and summary info to an Excel file for further manipulation. Perhaps years of TFS and VersionOne made the adjustment more difficult. Part of that might have been JIRA being new to me and not intuitive in ways. It seemed like either I couldn’t quite get just the information I wanted or it took too many steps. I tried different boards and settings, reports, and the Issue Navigator and JQL. Initially much of my time was spent trying to extract various detail and summary data from JIRA. I’d much rather be programming than doing such tasks so the more of that I can automate the better. That’s included things like status reports, executive reviews, client demos, general sprint and backlog management, and work distribution. See Working with Jira issues in Helix ALM for information.A current project of mine has no dedicated PM and I’ve had to fulfill some of those duties as the lead developer. The item opens with the Jira Issues tab selected. Click View all issues to open the Helix ALM item selected in the list window and view all attached Jira issues. The issue ID, summary, and status are displayed.ĥ. Click the attached issue information in the Jira Issues column in the list window.Ī list of attached issues opens. You can also add the Has Jira Issues column, which displays Yes or No to indicate if a Helix ALM item has attached issues.ģ. Right-click the column, choose Jira Fields, and then choose Jira Issues. See Changing list window columns and fonts.Ģ. See Working with requirement documents and Folders list window - Items pane.ġ. Tip: You can also view Jira issue information in columns when working with folders and requirement documents. To see up-to-date summary and status information, open the issue in Jira or navigate to details in the related Helix ALM item. ![]() You can quickly see which Helix ALM items have attached Jira issues in list windows. You may be prompted to log in before the issue opens. You can also click the issue ID or summary to view it. Click the Jira Issues tab when you are working with an item.Ģ. You can open Jira issues attached to Helix ALM items to view the details.ġ. Viewing Jira issues attached to Helix ALM items
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |