Skip to content

Structure for JIRA: Ideas

Thank you for visiting our feedback website! Feel free to vote or post your own ideas. Make sure you turn on the option to notify you about changes and comments in your account settings, so that you can stay updated about the progress of the ideas you’re interested in.

I suggest Structure should ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

31 results found

  1. Be able to set icon other than green check mark for different resolutions

    Currently if you resolve or close an issue and choose any option for the Resolution, the indicating icon is always a green check. I would like to be able to customize the resolution/icon combination. For example, set a red x if the resolution is incomplete, indicating that the task wasn't completed.

    Also, there should be options about how this affects the progress of a parent issue.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    declined  ·  Igor Sereda responded

    Using Statuses instead of Resolutions seems the shortest path to solution

  2. Integrate with Field Security Plugin to hide information according to field security configuration

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →

  3. It would be great if you can add Agile support.

    Currently we use bugzilla for bug and feature requests tracking.

    Deskzilla should have the ability organize the "bugs" and "features" into sprints, along with burndown charts etc.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    declined  ·  1 comment  ·  Admin →

  4. Configurable fields for "+Sub+Issue"

    We have the Component and Version fields configured as required for all issues, and so creating a sub-issue via the "+Sub+Issue" button fails since those fields are not available in the mini-create issue window. Is there some way to configure which fields are available in that window?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  5. Export to Excel File

    Printing is fine, but, I also need to export to an Excel doc. Is that possible?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  6. Don't break default browser functionality to open the links in a new tab

    I show the Key and Summary columns in the Structure View. Both columns contain a link, but Control-licking the link doesn't open the link in a new tab, which is default behavior in all browsers. Somehow the Structure plugin must do something to break that

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  7. If you manually change Epic field to point to a different Epic, the issue doesn't reposition under that Epic

    If you manually move the ticket under an epic, it will change the epic field value to that Epic. However, if you manually just change the epic field value to something else it doesn't reposition the ticket under that epic.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →

  8. Support the control enter key for creating of new issues as specified in the keyboard short cuts

    I really like the idea of mimicing the mindjet type keyboard shortcuts for creation of new issues. Control enter should create a new issue within the structure on the same level as the parent issue.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    declined  ·  Igor Sereda responded

    current keyboard shortcuts (Enter and Shift+Enter) are sufficient for creating issues and sub-issues

  9. Add a slight delay during drag-and-drop (so that parent nodes don't expand instantly)

    I think this will make it more easy to drag a child from one parent to another. It should behave like dragging files between folders in Mac OSX.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  10. Filter synchronizer should also scan newly created issues.

    Newly created issues matching a filter are currently not added in structures synchronized with that filter. This causes issues to slip trough the cracks by not showing up in the structure.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

  11. Preserve column selection & order in each individual Structure

    Different Structures server different purposes: test plan, release status, planning board, etc.
    Different goals call for different columns to be shown in each structure (based on purpose of each individual structure)
    Currently column selection and order is saved globally and applies to all structures, whether it makes sense or not.

    PROPOSAL: each structure keeps its own column selection/order

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
2 Next →
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base

(thinking…)