Loading Profile...
EMPLOYEE
Adding Linking Support to Mockups for Confluence, JIRA and XWiki
Hi there. So the linking feature is in Mockups for Desktop and it seems that most of the kinks have been worked out on it. It's time to bring it to the plugin versions!
I need your help with the design of the feature, and have a few questions:
What should show up in the link pulldown list?
Here's some ideas:
- in Mockups for JIRA, it could show all the mockups attached to the issue this mockup is on
- in Mockups for XWiki, it could show all the mockups attached to the page this mockup is on
- in Mockups for Confluence, it could show all the mockups attached to the page this mockup is on AND (perhaps optionally?) all the mockups attached to all the children of the current page (and their children too? This could get messy)
Other question:
What should happen when you click on a link?
I think the best option here would be to go "fetch" the linked mockup and show it to you, but when you get out of full-screen mode (with ESC), it should take you back to where you started (editing the mockup you were editing when you went full-screen).
All the other options seem messy to me (should it save and close? reload the editor each time? Yuck).
OK, I think that's enough questions for now. What do you think?
I need your help with the design of the feature, and have a few questions:
What should show up in the link pulldown list?
Here's some ideas:
- in Mockups for JIRA, it could show all the mockups attached to the issue this mockup is on
- in Mockups for XWiki, it could show all the mockups attached to the page this mockup is on
- in Mockups for Confluence, it could show all the mockups attached to the page this mockup is on AND (perhaps optionally?) all the mockups attached to all the children of the current page (and their children too? This could get messy)
Other question:
What should happen when you click on a link?
I think the best option here would be to go "fetch" the linked mockup and show it to you, but when you get out of full-screen mode (with ESC), it should take you back to where you started (editing the mockup you were editing when you went full-screen).
All the other options seem messy to me (should it save and close? reload the editor each time? Yuck).
OK, I think that's enough questions for now. What do you think?
I’m happy and thankful!
5
people like 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.
-
Inappropriate?I agree with your analysis. For Confluence, I think the mockups attached to current page would be good. Maybe an alternative to link to all the children of the current page would be to let the user select a specific page to find the mockup(s). So if I am in Space A Page 1, I can link to something in Space B page 4.
When you click on a link, just fetch the mockup as you suggested.
I’m happy
1 Comment
Add a comment
This is one of the best points
-
I thought of that, but going to find a page and a mockup on a specific page is an order of magnitude more "conceptual work" than selecting something from a pull-down (not to mention more work for me, but that doesn't really matter).
I wonder if perhaps the solution is to go with the simple "only the mockups on this page" as a start, and see how that feels. -
Inappropriate?In XWiki, I think the optimal behavior would indeed be to display all mockups attached to the current page to serve as linked mockups.
About the behavior when you click on a link in full-screen mode, indeed it should fetch the mockup and display it. However going out of full-screen mode is similar to going out of a powerpoint presentation -> the user might expect either to land back on the initial mockup he started from in edit mode, or the mockup he was currently showing in edit mode. Not sure which of both options would be best...1 Comment Add a comment
This is one of the best points
-
Thanks Guillaume...and good question about what should happen when you hit ESC. I am leaning towards the "go back to where you started" option because it side-steps all the ugly issues that have to do with switching from editing a mockup to editing another "on the fly"...like "what if the original mockup needed saving?" or "should I go to the edit URL for the new mockup (which involves reloading the editor) or let you save a different mockup from the initial URL?" - if you and others don't have strong feelings about it, I think I'd rather go with the "go back to the beginning" design.
-
-
Inappropriate?I like this idea
I think you need to be able to link to another mockup anywhere in Confluence.
I am using Mockups to design each page of our website and there is a confluence page per webpage.
Having the children of the page is perfect - but I might want to link somewhere else
I’m happy
-
Inappropriate?Thanks for the feedback everyone. I'm starting to think that a simple pull-down might not do for the Confluence / XWiki version, as much as I'd like it to.
Here's one option (which I don't particularely like), I have a couple more in mind which I'll post soon:
-
Inappropriate?Ok here's another idea...I'm not in love with it but maybe it's a step in the right direction?
I don't even know if Confluence and XWiki offer the right plugin APIs to implement this! :) I think they do...but I'd better check!
-
Inappropriate?OK a little improvement over the previous one:
The pulldown would also list the 10 most recently edited mockups on this computer...I bet those two lists would take care of 90% of cases, so that you'd have to resort to the Search dialog only rarely. Thoughts?
1 person thinks
this is one of the best points
-
1 Comment Add a comment
This is one of the best points
-
it's the last 10 mockups you edited on a particular computer, regardless of when you did it. Obviously some links might be broken if you renamed a mockup or moved its page around...in which case we'd show "[broken]" and disable that particular link
-
Inappropriate?Hi Peldi,
For the JIRA plug-in, it will really be handy to link to a mockup in any issue. When you link issues together in native JIRA, it will show you a list of recent ly viewed tickets or let you key in a ticket number to link to. I would expect the same kind of thing in MockUps for JIRA.
I agree that when you leave full screen mode, you should return to the original mockup you were editing. However, would it be possible to emboss the current ticket number (and link) on the mockup being viewed in the corner? The idea being that if you click the link, it opens in a new browser window (not sure how that would interact with full screen mode).
Here's the use case I'm envisioning:
-Imagine that we are designing a new feature with several dialogs that can be worked independently.
-We create tickets for each dialog and attach a mockup to each.
-We link the mockups together.
-We will review the tickets before sending to development by using MockUps in full screen mode.
-When we notice that something is wrong, I need a quick way to get into edit mode for that mockup (which might be several mockups deep). If I have a link to open that ticket in a separate browser window, then I can queue up multiple tickets to edit after the review session.
-Alternatively, what if there was a link in the corner to enter edit mode for the current mockup? So, that would be ESC to go back to the original mockup or click link to edit the current mockup.1 Comment Add a comment
This is one of the best points
-
Hi Mark, I like all of your ideas, as usual. I'll try to incorporate it all. :)
-
Inappropriate?Yes, it would be nice to be able to link to any issue in JIRA (ex: ABC-1234).
What if you suggested linking to mockups within the same ticket or, as Mark suggests above, mockups that are in JIRA issues that are linked to the current JIRA issue.
Then allow a manual way to put in any JIRA issue.1 Comment Add a comment
This is one of the best points
-
Right, so two lists: at the top the other mockups on the same issue, followed but mockups in linked issues, followed by a "browse..." command which opens a dialog which lets you input an issue #, similar to the Confluence/XWiki dialog.
-
Inappropriate?I'm not sure which APIs you are using, but XWiki and Confluence share the same XML/RPC api which can give you the list of spaces and for each space the list of pages, and finally the content of the page where you can find your mockups. Maybe the "More" menu could list you the spaces and then the pages. If XML/RPC is not so good and it might, REST might be easier. XWiki has REST apis for that.
I’m excited
-
Inappropriate?Hi there, just a quick note to tell you that I have added linking to Confluence, and would really appreciate your help in testing it. Here's the full story: http://www.getsatisfaction.com/balsam...
I’m happy
