• Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Every table, regardless of the type, could have this. For every user individually, start maintaining a list of column mappings for the tables that they care to customize. So, for example, next to each table that I view, we could have a button that opens a dialog, which then lets me rename columns to my liking. This should be saved in the database only for the user that defined such mapping.

      I understand that most tables are displaying issues, and that the question of how to treat global columns (issue properties) would come up: the answer should be, apply globally (per user).

      An example: if it bothers me that the column displaying a version number is too wide only because of its long name, I would rename it (by abbreviating); so, instead of "Targeted Version" I could have just "Target" or "tgt-ver", and I will then probably stopped being bothered by how wide that column is.

      Another subfeature: while the user is renaming the column, allow them to force a line-break. So, for example, I might dislike abbreviated names, so instead of "Targeted Version", I'd like to force "Targeted<br/>Version" (syntax can be invented), and I'll be happier to see that column less wide (while the title row/bar would become taller).

            [JRASERVER-23168] Custom, personalized columns that fit text

            Hi Hari,

            Thanks for your suggestions and I do see the merits in them, however custom personalised columns is not something we would add to JIRA at this time.

            Of course you can customise JIRA anyway you want and
            our local Atlassian partners will be able to help.

            Thanks again for your suggestion.

            Cheers,
            Roy

            Roy Krishna (Inactive) added a comment - Hi Hari, Thanks for your suggestions and I do see the merits in them, however custom personalised columns is not something we would add to JIRA at this time. Of course you can customise JIRA anyway you want and our local Atlassian partners will be able to help. Thanks again for your suggestion. Cheers, Roy

            hlubovac added a comment -

            Need I mention that you already have table customization system per user (rearranging columns for individual filters) - you would just need to add the ability to the UI to rename the column names also (which should be close to trivial), and the ability to persist and load those changes along with the rest of the metadata that is loaded for filters anyway (column order, etc). I'm sure columns are indexed across the system by unique IDs other then their names, so this doesn't sound too difficult at all (to me). You might need to expand the channel and the housing of that new metadata, depending on how you're saving it.

            hlubovac added a comment - Need I mention that you already have table customization system per user (rearranging columns for individual filters) - you would just need to add the ability to the UI to rename the column names also (which should be close to trivial), and the ability to persist and load those changes along with the rest of the metadata that is loaded for filters anyway (column order, etc). I'm sure columns are indexed across the system by unique IDs other then their names, so this doesn't sound too difficult at all (to me). You might need to expand the channel and the housing of that new metadata, depending on how you're saving it.

            hlubovac added a comment -

            might be partially repeating JRA-14428 and JRA-626, but this one (JIRA-23168) isn't the exact duplicate

            hlubovac added a comment - might be partially repeating JRA-14428 and JRA-626 , but this one (JIRA-23168) isn't the exact duplicate

              Unassigned Unassigned
              a1b4e736afae hlubovac
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: