Loading Profile...
Stronger JIRA integration (and versioning)
A proposal from our team:
In JIRA there is a ‘Manage Attachments’ option that takes you to the list of attachments, etc.
I think ‘Attach UI Mockup’ should be changed to ‘UI Mockup’ and it takes you to a screen similar to Manage Attachments.
From that screen see a list of .xml mockup files (it really needs its own file type and association) with the option next to file name:
- Edit
- Copy this to New Mockup
- Download
- Delete
Some people will want edit in place – replacing the old file name. But others will say that the old files are part of the documentation and should be retained. This solutions supports both groups.
When creating a new mockup you may pre-fill the name as date/time + “ - mockup” like ‘2008-08-21 14:21 – mockup.xml’.
Our preference is to pre-fill the name with:
date/time + jiraticket + ‘mockup’ as in ‘2008-08-21 14:21 TCCTWO-128 – mockup.xml’
This way you never have the problem of downloading and confusing it with another mockup file or ticket or version within a ticket.
Also, when you refer to a png file in the body of a ticket, that png will not keep changing as someone revises the mockup.
In JIRA there is a ‘Manage Attachments’ option that takes you to the list of attachments, etc.
I think ‘Attach UI Mockup’ should be changed to ‘UI Mockup’ and it takes you to a screen similar to Manage Attachments.
From that screen see a list of .xml mockup files (it really needs its own file type and association) with the option next to file name:
- Edit
- Copy this to New Mockup
- Download
- Delete
Some people will want edit in place – replacing the old file name. But others will say that the old files are part of the documentation and should be retained. This solutions supports both groups.
When creating a new mockup you may pre-fill the name as date/time + “ - mockup” like ‘2008-08-21 14:21 – mockup.xml’.
Our preference is to pre-fill the name with:
date/time + jiraticket + ‘mockup’ as in ‘2008-08-21 14:21 TCCTWO-128 – mockup.xml’
This way you never have the problem of downloading and confusing it with another mockup file or ticket or version within a ticket.
Also, when you refer to a png file in the body of a ticket, that png will not keep changing as someone revises the mockup.
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
The best point from the company
-
I have implemented stronger JIRA versioning by doing something different:
- mockups now loads all existing mockups attached to an issue on load, so that you can edit one easily
- mockups now only keeps the last version of the image and all versions of the data are accessible
- added a "save as new" option to create mockup modifications
- added an automatic naming convention for new mockups, which uses the current date and time (so that it's easy to sort many mockups)
The company thinks
this is one of the best points
-
Inappropriate?Not knowing yet if any of this is possible, I like where you are going with it. One thing I'm not sure of is to replace the "Attach UI Mockup" link with the always-there "UI Mockups" section. I think the section should be there only if there are mockups attached to the issue. But it's a minor thing. I'll try to make some time next week to dedicate to making this happen, or at least learn about what's possible and what isn't.
Adam, thanks for helping me with this, I appreciate it.1 Comment Add a comment
This is one of the best points
-
Agreed, the "Attach UI Mockup" link is always present and the "UI Mockups" only shows when the ticket has 1+ mockup.
We look forward to seeing some great stuff! -
Inappropriate?If the whole "Manage UI mockups" makes it through, it would be great if on the issue's main screen if it would show a png of ONLY the most recent mockup (eliminating the problem of deciphering which image represents the most recent mockup).
I’m floating ideas
1 Comment Add a comment
This is one of the best points
-
Thanks for floating ideas, it really helps. One issue I have with this particular one is that from my understanding people use JIRA more and more for feature specifications, so one issue might have more than one, equally important mockups on it. I wouldn't want to hide important things...
-
Inappropriate?That's probably true. We use it a specific way where each issue or sub-task is a specific screen, but you're right others might want to show more.
Which brings me to... yes, a new mockup. =)
-
Inappropriate?I have implemented stronger JIRA versioning by doing something different:
- mockups now loads all existing mockups attached to an issue on load, so that you can edit one easily
- mockups now only keeps the last version of the image and all versions of the data are accessible
- added a "save as new" option to create mockup modifications
- added an automatic naming convention for new mockups, which uses the current date and time (so that it's easy to sort many mockups)
The company thinks
this is one of the best points
EMPLOYEE
