AgileTrack
Put your development on the AgileTrack

Tab Naming Suggestion

As somebody looking at agiletrack for the first time, I would like to make a suggestion. It seems to me that, whatever it used to be, the Issues tab is no longer an Issues tab the same way that the Projects, Iterations, Revisions, Users, and Queries tabs are. I mean on those tabs you have a list on the left panel, and details on the right. But the Issues tab is, to me anyway, the REAL Search tab. You define the queries on the Search tab, but you actually run them on the Issues tab.

So anyway, my suggestion is to rename the "Search" tab to "Queries" and to rename the "Issues" tab to "Search".

And am I wrong in expecting a list of existing issues above the "New Issues" button on the Create tab? Maybe issues not associated with a project should show up there, and it should be called "Issues"?

James

—Posted by James on Dec 9, 2006


	Forum AgileTrack Client


	Reply

I disagree. Issues tab shows issues. there are different views (list, grouped by iteration, grouped by project, etc.) but the main purpose is to see issues. "Search" name doesn't reflect the purpose of the tab, to browse issues. Maybe "Issues" is a little confusing, since it's not simple issues list, but it's much better then "Search"

btw, you define queries in "Queries" tab

—Posted by slava on Dec 10, 2006 at 11:21:20 AM

I see your point with the Issues tab. But the version of agiletrack I'm running (8b) has the tabs being (from the top) Home, Search, Issues, etc. The screenshots on the website have Home, Search, Tasks, etc. So if you have renamed the Search tab to Queries in future versions then that give me a warm fuzzy in a anal retentive sort of way.

BTW, my Create tab has a list and a button on the left that is missing on the screenshot Create tab. I much prefer the screenshot version.

James

—Posted by James on Dec 11, 2006 at 9:32:49 AM

The screenshots are definitely out of date. That'll get taken care of eventually.

The list on the left is for creating templates for issues. This may not be useful for most people, but the idea is that some of the content for particular issues can be stubbed out in the template.

For example, maybe a defect is always supposed to list the steps to reproduce, the failure condition, and the expected results. Simply fill in the stub information—name=Bug, type=Defect, description="Steps to reproduce… Results… Expected results", etc. Then click on "Template" and that saves the issue as a template listed on the left that can be selected to reuse the stubbed information. It's not the most intuitive thing, but it's useful for some people.

I think I'll make it a System Configuration option whether or not to use issue templates. Then it would look like the Create tab in the screenshot if desired.

—Posted by Adam Lane on Dec 13, 2006 at 7:19:12 AM

Actually I like that idea, I had no idea that's what it was for.

James

—Posted by James on Dec 13, 2006 at 9:06:35 AM