Viewing issues completed in released version - jira

Is it possible to view a list of completed tasks in a released version?

Yes, of course. If you go in a current JIRA version to your project, on the tab name Versions and click on a released version, you have a view with only the issues of that release.
You may alternatively create a query with the following:
Select from the menu: Issues > Search for Issues
Select your project in the list of projects.
In the blue box below, press Refresh Search.
Select the version under Fix for.
Press the button Search above.
If you need that search again, just copy the link under and keep it in your bookmarks or it as a filter.

Related

Adding a drop down on issues screen

Whenever there is a new release of an APK, I create a release version under the project
releases option in JIRA. And now, when creating an issue, I put the newly created version
in the affectedVersion field.
But now, when I have to search for all the issues in this version, I have to write a JQL
like project = "BA" and affectedVersion=2.0-uat-2 order BY created DESC
Is there a way to avoid writing this JQL and instead have a dropdown for affectedVersion
which shows all the versions. This way, there will not be any need to write a JQL manually

Use target version for release planning in JIRA

We have JIRA issues with the following fields:
Affects version - version where issue is noticed
Target version - version in which we want to fix the issue
Fix version - version where issue is really fixed
The release planning is based on the fix version, I suppose per default. How could it be changed to use the target version? We set the fix version when closing an issue, so it is not at all appropriate for the planning.
"Affects version" and "Fix version" are system fields in JIRA and various screens are based on them. This is logic that you cannot change.
The "Target version" is not a default JIRA field, so it must have been added as a custom field on your instance.
Instead of trying to change the concept of a "Fix version" you're better of using it as it is intended by JIRA and customising your own logic with custom fields that you add yourself. Otherwise screens like JIRA's "Releases" view will not behave as expected.
So you should use the "Fix version" field to plan the target release and update it with the appropriate version if the actual release changes. For any other kind of version info that you like, introduce your own fields.
In the "Releases" view you can click on "View in Issue Navigator" on the right side:
This will show the JQL that is used by that view and it will show something like:
project = 12421 AND fixVersion = 17740 ORDER BY priority DESC, key ASC
This is hardcoded and I don't know of a way to customise this.

How to view/compare a file's history in Delphi?

The title says it all. I made some changes & closed/re-opened Delphi, so I Can't use Ctrl-Z to undo my changes.
How do I compare the current file with previous versions?
For code only, if you don't have a version control system installed, you can view recent changes by using the History tab at the bottom of the code editor window, and then click the Differences tab. How far back you can go depends on how you've configured it; the default is 10 revisions. You can change the default in Tools->Options->Editor Options->File backup limit.
In the absence of any other revision control system there is a History tab in the code editor window - from there you can view a side-by-side diff with previous saved versions by using the Differences tab.
If you installed BeyondCompare with XE8 then you can also access a revision history of your files by selecting (with the file of interest open in the IDE)
Edit -> Compare -> History Compare...
This will present you with a list of saved revisions. Select one and click the Show Diff... button to present a side-by-side comparison.
Going forward, I would seriously consider using dedicated revision control. Commit often and this type of situation should never be a problem for you.
if you have a version control system then use this.
else: if you use Win7 then right-click the file, choose properties and see "older versions". You have to have enabled this Win feature beforehand...
else: your previous versions are lost

Jira - Versions button not displayed on Project Overview tab

When I go to the Overview tab of any project I get five options:
Summary, Issues, Reports, Popular Issues, Labels.
I can create Versions via the Admin tab.
However if I look at an Atlassian project I can see a 'Versions' button on the Summary page.
Tried to include a URL to it but SO will not let me.
This 'Versions' button gives a very handy report of the Versions & a version can be selected to give a detailed report of that Version.
How can I add this to my summary ?
If I add the URL params I get nothing as in
my_server:8080/browse/MY_PROJECT?selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
We have v6.1.2
Sadly I have just found at that this is only possible for SCRUM style Jira projects. I found this page 'Viewing the Version report' which says it only works for SCRUM projects
Why JIRA Why ?
Why on earth would I not want to be able to list the issues in such a convenient way. Instead I have to create a unique filter for each version.
The project reports such as Summary are not customizable. The Versions tab only appears after you create your first version, which is not always obvious.

Find shelvesets via Visual Studio as quickly as possible

I need to review many shelvesets using Visual Studio every day. I have added the TfsPendingChanges command to the my toolbar, but the rest of the procedure to access a shelveset (Actions/Find Shelvesets) still feels clumsy. In fact, shelveset review has nothing to do with my own pending changes. And VS11 just made it even one step longer than it already was.
Is there any way to add "Find Shelvesets" in some form directly to a menu or to a toolbar, in Visual Studio 2012?
If you go to right click and then "Customize" on any toolbar, it will bring up a dialog. Press the "Keyboard" button on it, choose File.TfsUnShelvePendingChanges and assign a Hot Key to it. I do believe that the Source Control Explorer window needs to be open and active for your hot key to work.
OR...This may not be exactly what you are looking for, but if you have the Source Control Explorer window open and active, then ALT-F ALT-R ALT-F ALT-F ALT-S will bring up the dialog. That is actually navigating File/Source Control/Find/Find Shelvesets.
The easiest way to work with Shelvesets is to use the new My Work feature. By suspending and resuming work Visual Studio will automatically do all the Shelveset magic for you with a simple drag/drop of the task that you want to have in progress.
The same applies to reviews, Suspend your current work, or create a new temporary workspace, open the Review Request, let it unshelve the changes automatically and when you're done go back to where you were by resuming your previous tasks.
It's really great once you get the hang of it. That it uses Shelvesets under the hood is nice to know, but this way you don't really need to know, it just works.
As for TWA Diff, there've been great improvements with TFS 2012 Update 2 which is almost ready to be released...
If this is only for reviews then maybe Team Web Access would be better for you?
Just navigate to http://:8080/tfs/web/, select team project, then click Source Tab and Find Shelvesets. You can then open each shelveset in new browser window and it will list all changes and allows you to quickly do compare etc.
Command that you are looking for is TfsUnshelvePendingChanges under File.
Right click on any toolbar, click on customize and a dialog will open. Go to 'Commands' tab on the top.
Choose appropriate button out of Menu Bar | Toolbar | Context Menu. Select the desired option under that. My favorite is to add it to Toolbar>Work Item Tracing (toolbar where New Item/Open Item appears).
After choosing from above step appropriately, click on 'New Command'. Then select to File>TfsUnShelvePendingChanges. This will add a shortcut to unshelve changes.
Thanks to #Alex for pointing out the correct command name. Writing here separately for people looking for answers in future.

Resources