@Sarah Hyne Hey thanks for providing some insight into your testing methods! I'm keen to hear more about the internal expert evaluations against usability heuristics. I'd also be interested to know more about the evaluations with customers... More around the sample size for validating new features, how do you evaluate what sample size would be appropriate? Or do you keep validating features with customers until you stop learning new insights (to an extent obviously)?
The updates look like a good step forward in many ways! I like to see these as quality-of-life updates.
@Liron The "3-state issue create experience" isn't entirely-clear to me.
I personally prefer the center-view when creating issues and don't see myself using the bottom-right widget all that much. From the looks of it, now that there's this new widget, instead of one-click to invoke the new issue form, I now have two clicks to perform โ one to click the "Create Issue" button which open the widget, then another click to expand it to center-view.
Will I have to perform this extra click each-and-every time I want to create a new issue, or will the application remember what view I was last using when I click the "Create Issue" button?
Good job! I like the changes. I see that when you minimize the issue, it is only visible in the current tab but if you opened another tab this does not appear, it would be great if it could be seen in all tabs.
Another important change that could be worked on would be to make the site responsive. Our instance is not responsive and that sometimes limits us a lot, specifically when administrators work with ScriptRunner because we don't see all the code. If I am doing something wrong, please let me know.
>Change the default status of newly created issues to either โIn Progressโ or โDoneโ, rather than just โTo doโ.
How does this operate? Does this take the issue through transitions to the targeted status? Or does this effectively re-target the "Create" transition to the targeted status?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
First, thanks @Liron and the Atlassian team for all these great features, we are looking forward to using them.
@Bishopjustice , I too, am pleased to see the inline editing available directly in the backlog, I believe this would be a great time saver.
At Elements, where I work as a Product Manager, we developed a complementary app, Elements Overview, that allows you to inline edit related issues in the context of an issue: it can be linked issues or even issues matching a dynamic JQL.
Moreover, you can display any custom field you like of related issues, and also edit them from the current issue.
In this example, we chose to display 6 fields, and inline edit the due date directly from an overview:
If any further information is needed, you can @ me here, or schedule a quick call if necessary.
This is great! I have been looking for that feature.
There is just one glich โ it doesn't work, at least in Microsoft Edge. When you click Minimize or the other Resize button, modal disappears completly. When you click "Create" one more time, there is message with "back to edit" option.
@Liron thank you for the updated features. Are there plans to change who you can assign an issue to without it being assigned to yourself first if I already know who the ticket needs to be assigned to? From my limited experience, I have had to assign an issue to myself first prior to moving it to someone else. If there are other ways of accomplishing this, please let me know.
@Lironthank you very much for these useful features.
For some, such as "Reference attachments" I have eagerly waited so long, as I often reference already uploaded attachments in my issue comments.
I was wondering though, why did you choose to launch all these features at once in one rather big feature set instead of in smaller iterations? Wouldn't that have led to some of them being available sooner?
Lastly, a small feature proposal:
Additionally, to the "Assign to Me" option, we would love to have a "Unassign" option as short cut, as this is a very common process in our projects. Certainly, that does make sense for projects/companies which allow to have unassigned issues, only.
Atlassian Team members are employees working across the company in a wide variety of roles.
January 9, 2023 edited
Hi @Krzysiek Czuba I'm one of the developers working on this feature and would love to help out.
I was looking into this issue, and am having trouble reproducing your issue on Microsoft Edge. Could you let me know what version of Edge and what OS you are using? A screen recording would be perfect as well.
Atlassian Team members are employees working across the company in a wide variety of roles.
January 9, 2023 edited
@Yatish Madhav โ If you're interested in being part of testing new features, you can sign up to our Atlassian Research Group where you will be invited to participate in upcoming research. Participation is voluntary, and you can opt-out at any time.
@Brad Richards โ The internal evaluations we run use the PURE methodology. We also run reviews of key workflows using an internal scorecard. Both methods have a crew of cross-functional Atlassians taking part. Around sample size, "it depends" is the answer! It depends on how many customer segments we need to test with, and how confident we are with the solution we've come up with. In any given round of research we would, as you said, stop once we keep hearing the same feedback. We might conduct many rounds of research as we iteratively design and test a solution to a problem. Hope that answers your questions!
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Super! Thanks for that @Sarah Hyne and for your comment @Brad Richards - the heuristics and the process followed is insightful! Esp coming from a background where were also support our customers (internally and externally)
I have also signed up for hte research group. Looking forward!
@Sarah Hyne Thanks for the insightful response! I've definitely heard about PURE although I've never used the method in a live environment before so I'd be keen to eventually try it on my side. I'm going to do further reading on the topic! Reviews of key workflows also sound interesting.
The sample size conditions make complete sense. Once again thanks for clarifying and answering my questions. ๐
73 comments