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.

98 results found

  1. Add a column separator

    I'd like a light visual separator of column.

    I use multiple notes to fill custom data for each ticket and when double clicking to edit the values it's not easy to know which column I'm editing

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Respect Worklog view permissions or hide work log author filter in Data Center

    Structure DC introduced author filters for worklog columns. Unfortunatly, not all columns respect the rights from Tempo Timesheets so if users have only read access to a structure with issues they can effectivly build timesheets for other users, even if this is effectivly forbidden in Tempo Timesheets through Team permissions or View all worklogs project permissions.

    This is a huge issue for us as it goes against our Privacy/DSGVO/Union regulations and is prohibitive to a further rollout for structure.

    From what I gathered the "Tempo Work Logged" column behaves correctly and respects the permissions.

    On the other hand, the standard…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Export to Word

    We'd need the possibilty to export the structure to a Word document. This should apply hierarchy levels for headlines and also include rich content such as embedded images (e.g. in description).

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Support Rich Text In Note Columns

    Note Columns don't support any formatting currently, also line breaks are ignored when a note column is displayed.
    Rich Text editing and display, based on markup or a rich text editor, would be great.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. How to create task templates

    Choose a Tool: Open your project management tool or document editor.

    Create a New Template: Start a new document or template file.

    Define Tasks: List the main tasks you need regularly.

    Add Details: For each task, include steps, deadlines, or any important notes.

    Save Template: Name and save your template for future use.

    That's it! You now have a reusable task template.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. integrage Jira Asset Management Fields

    I propose integrating Jira Asset Management with Structure to elevate the management of asset-related data. Ideally, this integration would enable the grouping of Asset Fields, simplifying the display of these fields in dedicated columns within Structure for enhanced organization.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. activate/deactivate individual transformations in a group

    Hello!

    We currently have an issue with grouping transformations. We try to improve organizing them and we would like to use the grouping function for that. The issue is that in a group, every transformation is always active. We would like to be able to deactivate some of transformations in a group by hand. It seems like this should be possible, since you can expand a group to see the individual transformations, but you are not able to click on them to deactivate.

    This is very unfortunate, since we would like to use this to categorize the transformations. In some…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Automated Export of Formula-Based JIRA Structure Reports

    I propose the introduction of a feature that enables users to automatically export JIRA structure reports, particularly those built using formulas. The export functionality can be facilitated through a REST API or a scheduler, with outputs in the CSV format for example.

    My need for this feature arose when I attempted to retrieve the report via the existing API, only to realize that the current system doesn't support this (I can only get list of standart attributes). A review of the documentation confirmed the absence of such a feature.

    Thank you for considering this suggestion.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow compact summary column

    The mandatory default summary column includes seemingly unnecessary leading empty space.

    I have multiple structure boards in a two-column jira dashboard enabling quick overview of my daily tasks. The horizontal space is therefore very precious and I use a separate "compact" view showing only priority, id, summary, and perhaps status of the issues.

    There is currently no possibility to make the summary column more compact, since the summary column cannot be deleted or minimized to make room for a custom one.

    The leading whitespace seems to be caused by <span class="s-expander s-fa"></span>. I suggest either removing this whitespace completely…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Share views with specific structures only

    When sharing views they are shared globally across all structures. Whereas often a view is optimized for a single structure. Setting the default view allows you to have an optimized view for a single structure, but then it is difficult for other users to know what other views have been optimized for a specific structure.

    This could be solved by allowing sharing of views to be limited to a single structure. Or providing an option for what structures you want to share a view with.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add sequence or ID for Issue Item Property

    It would be helpful if the "ID" would be available as an Issue Item Property, similarly as key or summary etc.

    It would be useful for example: As an admin I need to go to database and find some rows in tables that are using issue id as a reference column.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add activatedDate property to Sprint item in Formulas

    Jira Structure Formulas currently provide following Date type properties within Sprint item: startDate, endDate and completeDate:

    https://wiki.almworks.com/documentation/structure/latest/data-center-and-server/item-property-reference-168558906.html#id-.ItemPropertyReferencev8.2-Sprint

    When I compare it with official Jira REST API, it seems that there is missing activatedDate property:

    https://docs.atlassian.com/jira-software/REST/9.5.0/#agile/1.0/board/{boardId}/sprint-getAllSprints

    Would it be possible to extend Sprint item object with activatedDate property, so that it’s possible to access this value via Formulas column using Expr language?

    Usecase is to create Structure which shows same level of information as original Jira Sprint Report page, however currently it's not possible to mark issues which were added to the sprint after it's start (activation), because of missing access…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Support variables / formulas global to a view or structure

    In Structure 8.2.0, you introduced the ability to save and share formulas. Once the formula is loaded, it is stored to the new column and not impacted by any changes to the source formula.

    This does not any real-time if the formula has been shared in many locations. Updating a variable formula involves several steps (not sure reloading is much quicker).

    It is also a quality risk because the user has to make sure any updates have been made everywhere. it takes several steps to verify the updates were made.

    variables/formulas global to a view or structure would support the…

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Support Parameters (per structure) for transformations

    Basically I create a structure per version of my application and I use automation to insert issues based on certain filters that are for the given version (e.g. bugs with certain properties for this version etc...). Not everything is inserted by automation, but there are several places where I use automation for inserting. Thus every time I create a new version, I have to "find" all these insert automations and modify their filter to match the new version: Not really a problem, but it would be very nice if I could somehow specify the version as an attribute of the…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add ability to Extend by Formula

    Grouping by the result of Formula is very robust - it is possible to produce literals as well as arrays.

    If it wolud be possible to Extend by Formula instead of the links and subtasks and Epics only, it would give the power of extending based on the content of the Jira ticket, which may contain i.e. fields with issue list.
    It would by possible to construct deep structures with issues not linked to other issues but having them listed in some fields.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add a vertical option for "Grid + Details" Layout

    Currently when using the "Grid + Details" view it only provides the ability to view the issue details in a panel to the right side of the structure view.

    Many engineers however tend to use their screens in vertical mode and thus this side-by-side view is less than ideal as it gets cramped fast.

    For these users, it would be really nice to have another option for "Grid + Details" layout where the issue details panel appears below the structure hierarchy panel rather than to the right.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Save and share column width, transformations, hierarchy levels and other customized settings

    Now it is not possible to have column witdth to be saved and shared with other users or set this by default for structure, but it could be very helpful when working with large number of columns. The same is with transformations - you now should share structure with share link instead of general link for structure, but it will be better to save all kind of this settings in view along with columns, columns orders etc.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Have an access to worklog via issue in formula

    With 7.4 version there is an ability to have history access via structure item (history) or via issue.history. But there is also possibility to access worklog wtihout possibility to access issue.worklog, which makes impossible in formula to navigate to worklog of linked issue. I believe that worklogs could be also accessed by issue.worklog

    Yes - it is possilbe to make this through structure attributes when you add child issues but it is like creating formula in excel using same column for calculation - doesnt seem reliable.

    Thanks in advance! Happy to use such great, useful and advanced product!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Add description option to Structure Views

    It would be a better experience for our users to see the View creator´s description for Views (at least mouse hover info). We are using very complex Views that are not self explanatory

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add a View control option for quick transformations

    We are extensively using quick transformations as "one-button perspectives" on complex Structures. So e.g. we are providing transformations like "show risk issues only". What is hard for us to convey to our users is that clicking this transformation, they must (manually) switch to the View designed to see the right columns for risk issues. If we could have the possibility to tell Structure in the quick transformation settings that clicking a specific transformation would automatically change the View to a specific one, this would shift the magic for our users to the next level :-)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Structure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5
  • Don't see your idea?

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base