Looking for ideas.......

[Dana Jansen - Confluence Queen]

We would like to get a survey of the top 10 ideas/things our Community members want to see or do over the next 12 months.

Some Examples....

Workshops?

Vendor Presentations?

Community Member Presentations?

more Q&A

Features & Functionality

[Dana Jansen - Confluence Queen]

@all

We would really appreciate any feedback or any ideas.

[Monique vdB]

@Andrew Yarrow, @Mark Richard, @Amy_Hall, @Fadoua, @Daniel Eads {unmonitored account}, @Carol Jones, @Rachel Wright -- any thoughts? 

[Rachel Wright]

I've always wanted to attend a methodologies presentation.  What philosophy does your team use?  How does your methodology influence your use of Atlassian tools?  How do you technically and culturally manage a philosophy shift?  etc. 

[Alex Baldwin]

@Dana - I think you need to drop the 'Confluence Queen' from your title.  We can't @mention you on here without having to "Billy it" every time.

Having hands-on working sessions with a plugin or app is always great.  To Jay's point, it would be great to have an AUG centered on Bamboo but you either know it all the way or not at all; it wouldn't be great for those not dealing with automation.

[Fadoua]

Yep those parentheses are killing me I can't tag Billy and Dana.

I agree with @Alex Baldwin hands-on working sessions are my favorite. I also asked Billy yesterday if we can learn more about Bitbucket,  or may be sourcetree, clover or a plugin like Adaptavist ScriptRunner  so that we can extend our knowledge. The learning session can take more than one meetup if needed as long as the presenter is ok with it.

[Billy Poggi AUG NOVA_ DC]

@Fadoua this is all perfect stuff.  

Here's my other account also, @BillyP  <- less edits required :)

[Huey Callison]

+1 to the last two. This new 'community' thing is nice, but what I think the AUG could really benefit from is demo projects in the actual tools. We can sit around and drink beer and TALK about whatever cool stuff you're doing in JIRA or Confluence or Trello or whatever, but if you really wanna grab people by the braincase, give them a hands-on demo. Write an ugly shellscript that creates a couple hundred JIRA tickets and then show off your mad dashboard design chops, and then let people experiment on that. Take something you built in your own confluence, replace the proprietary text bits with Lorem Ipsum, show people how to do fancy page design, and then let them goof around with it. Show people how to write a query in the Confluence jira plugin that crashes both of them, explain why that happened, and then show people how to prevent it. And so on.  

[Billy Poggi AUG NOVA_ DC]

These are all fantastic Ideas!  Thanks @Huey Callison 

[Diana Carter]

+1 to seconding Huey's ideas.

[Carol Jones]

The below discussion has so many concepts that I'd love to do a deep dive on.  I agree with so many of them, but sometimes have a hard time explaining the benefits to users/leadership as it's just common sense in my mind.  Would love to hear how others are setting themselves up for success and potentially even share some of your user comms around this topic.

https://community.atlassian.com/t5/Jira-discussions/What-would-be-your-advice-to-first-time-Jira-Software-admins/td-p/711667/page/2?utm_content=post&utm_medium=email&utm_source=atlcomm#U830666

[Dana Jansen - Confluence Queen]

Different implementations/use of the Atlassian Suite

• other than software
• Education? ( I see LOTS of college/universities using the suite)

Success Stories?

• Large implementations
• Small implementations
• One app
• Multiple app
• Phased approach

Common Mistakes and Assumptions?

• Users make
• Admins make

Common Themes?

https://community.atlassian.com/t5/Jira-discussions/What-are-common-themes-you-ve-seen-across-successful-amp-failed/m-p/714720#M2038

[Huey Callison]

The single-user/small-team JIRA "to-do list" implementation: a 10-user server license, a simple workflow (to-do | blocked | in-progress | done ), some simple filters, a simple dashboard, a calendar, etc. 

If Atlassian doesn't want to pony up some demo space, it'd cost ten bucks for anybody who wanted to do the hands-on, but you could totally run through that in an hour, and touch on a bunch of more advanced concepts along the way. And some of those are bound to come up. 

"Hey, how do I create a post-function at ticket creation that looks for dependencies that aren't 'done' yet and automatically puts the new ticket in 'blocked'?" 

Point being: be agile. Start small. Bolt more shit on as you need to.