118 results found
Now it's only icon...1 vote
When viewing an issue of type “Test”, created by Zephyr and assigned to a Structure, we are not able to see the corresponding Structure section as expected. If we change the type of the issue to anything else (Bug, Story, Epic, etc.) then the Structure section becomes visible. It seems that either Structure or Zephyr is not playing well together. This is critical to our organization as we try to integrate structured testing into our organization.3 votes
Currently, when inserting this gadget in Confluence, the Structure is completely collapsed. Is there a way to give the user the ability to change the default setting for the structure to be fully expanded?1 vote
We added 2 custom fields for testing steps. The carriage returns show up in Printable Page nicely. But we can just print that. The Excel export doesn't keep them and so the steps are jumbled in each cell instead of a clean representation.4 votes
I really appreciate the ability to edit tasks directly in the structure view. However, doing so results in two undesired side effects:
If the user needs to change multiple fields, they have to do so one field at a time. Depending on the notification scheme, this can result in a lot of email spam.
It encourages users to change fields on the issues without entering associated comments. For example, if somebody is changing the Fix Version/s for a task, in our team, we expect them to enter a comment explaining/justifying the change. There is no way to enter a comment…
Greenhopper's Agile plugin allows for nested "versions" to define Agile Sprints within a top-level planned release. This is represented in JIRA as comma-separated items in the Fix Version/s column.
The Agile Planning Board is smart enough to show the last Version in that comma-separated list indicating the current sprint to which an issue is assigned. Structure is showing all the comma-separated versions which takes up a lot of column width space (particularly considering the Structure view does not wrap text in columns...).
Would you consider creating an Agile Version column that is essentially the last item in the Fix Version/s…3 votes
will be possible with configurable and extendable columns
For adding / deleting issues from the filter in background mode1 vote
When you filter with JQL in structure, the hierarchy below is not shown if sub issues don't match the filter.1 vote
Structure defaults to no permissions to anyone. Admins should be able to set a default permission scheme for any new structure that is created from that point on.3 votes
So that I can restore the state of the view from browser history (using back button etc.).7 votes
The structure view should allow the user to display "attachments" as a column, where attachments are listed similarly to the "Images" column. Clicking on an attachment thumbnail would popup a preview of the attachment.
At the very least it should allow the user to download the file without opening the ticket itself.12 votes
By specifying some fields e.g, priority and assignee as well as the indendation level of the issue while entering the summary text of the issue will speed up the data capturing with structure. Please consider having a look at www.checkvist.com for effective keyboard support for increased speed and useability.
Eg use the @ to specify the person eg @john
use the # sign to specify the priority
Eg #0 - blocker
Tab indentation in the summary for instance indentation level 1 specified by 1> indendation level of 2 specified by >2
Similar to functionality in Greenhopper and other plugins, add a button to structure to allow opening the list of issues visible in the structure in the Issue Navigator.
I use the Agile Cards plugin. It's possible to print cards from the Issue Navigator. I would like to be able to print cards for a portion of the hierarchy in a Structure but I have no way to get from the structure to that functionality. One possibility is to allow opening the issues currently visible in the Structure in the Issue Navigator.
It seems like this would be useful for other…12 votes
I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.
Alternative (even better): automatically detect sub-issues for certain link-types13 votes
planned after 1.0
It would be nice to have the ability to dump the structure board to a csv. Thinking that it would be something quick and dirty, with ' - ' noting structure, like this:
"Name", "Est Hours", "Progress"
"Mars Colony", "10h", "80%"
" - Terraform", "6h", "50%"
" - - Make Oxygen", "2h", "100%"
" - Create Colony", "4h", "0"
Once this was CSV, it could be manipulated in other programs. Right now, I don't see a way to get the Hierarchy or estimate roll-up data out of the system for project managers to use.3 votes
Let JIRA admin specify what issue types could contain what other issue types. For example, a Test Suite may contain Test Cases, which can contain other Test Cases, but not Feature Requests.86 votes
Let the user specify, for example, that all sub-issues of the issue X should have the same Security Level and Project and Priority.65 votes
- Don't see your idea?