- 📌 Jira Cloud for Google Sheets app is staying
- 🏘 Appfire Town - a global social impact program
- ➡️ Restrictions on usage of issue-level grants with Project permissions
- ➡️ New permissions to replace Browse Projects permission
- 🗓 Weekly Atlassian Events Roundup
- 🎉 Join Us at JiraCon 22 (Use JEXO10 code for $10 off)
- 👥 WorkLife, a brand new in-person and digital event
- 📚 Article of the week: Six ways we’re making Custom UI Bridge more powerful
Jira Cloud for Google Sheets app is staying
Let's start with a deprecation update that was posted on the community last week. If you noticed an announcement about the depreciation of Google Sheet integration for Jira Cloud and were disappointed, I have good news for you!
The Atlassian team decided to keep the plugin that allows integration between Jira Cloud and Google Sheet after receiving much valuable feedback from the Community.
Over 120 comments helped change the direction and saved the plugin. This shows that the Atlassian team listens to the feedback of the community. So if you ever have thoughts on the updates and feedback on Atlassian products, share them with the community, it's worth it.
Appfire Town - a global social impact program
Last week Appfire published a post and a video introducing Appfire Town. This initiative is Appfire’s Corporate Social Responsibility Program with the goal to generate opportunities for social impact.
Yet, the Appfire Town program extends to the entire Atlassian ecosystem and beyond.
So listening to Fabian Lopez, community leader, speak about it, anyone outside Appfire can be part of it. Anyone who wants to make an impact, can become a member of the program or, as Appfire puts it, a neighbour in the Town.
The way this works is not by Appfire triggering the initiatives, their role is to support those who want to put time and effort towards a certain cause. Fabian and the team will support folk eager to make a difference by providing the tools for you to succeed. Be it financial support, supplies, and resources or guidance and encouragement.
Appfire Town has already supported a list of initiatives:providing supplies and transport for families in Ukraine, helping an organization that supports wounded and disabled veterans, supporting Autism therapy initiatives, organizing a global blood drive campaign, and many more.
So if you have a cause that's dear and near to you, read this article explaining the program in detail, then reach out to Fabian to set things in motion. It's worth mentioning, that you don't need to have a cause, if you're eager to help with some of the existing campaigns.
Do reach out as there are infinite ways you can support Fabian and the Appfire Town team.
Restrictions on usage of issue-level grants with Project permissions
And now to the updates to the Atlassian products, last week the theme was all around Jira permissions. There were two change announcements, so let's have a closer look at them.
1️⃣ The first one is related to restricting roles that you can assign to your project-level permissions.
You won't be able to add current assignee, reporter, user custom field value, and group custom field value to your project permissions anymore.
Assigning these roles was a bit tricky because it gave the Administrator project access to entities, which would open up the project to users you might not expect.
Check your project permission setup and see if you're using any of the mentioned roles. If so, check out the community post to see full details about this change.
New permissions to replace Browse Projects permission
2️⃣ The second update is a larger one - the 'Project browse' permission is going to be deprecated and replaced with two new permissions - 'View project' and 'View Issues'.
The 'Browse project' permission allowed you to do both: see the project and see issues from the project at the same time. But many of us had the need to only allow seeing projects without the ability to see issues inside. And these new permissions allow you to do exactly that.
'View Projects' permission is a project-level permission allowing you to view projects in Jira. For example, you'll be able to find the project in the drop-downs across Jira, e.g. JQL, and on your Projects page in Jira.
'View Issues' permission is issue-level permission for viewing the issues within a project.
This is a big change, as Jira admins, take time to read this announcement and get clarification from the Atlassian team.
This also affects Atlassian Marketplace Partners - if your app is using 'Browse project' permissions.
Have a look at this post to see what changes you need to apply to your apps.
Weekly Atlassian Events Roundup
This week on Thursday we have the third and final week of Lightning Talks series about the Marketplace - deep dive on Business apps and DevOps apps available on the Marketplace.
There's also plenty happening this week in the Partner-organized and Community-organized events with meetups every day.
Have a look and find the right events for you at Goosly!
Join Us at JiraCon 22
JiraCon22 brings together the Atlassian User Community, the Atlassian Marketplace Community, and Worldwide Atlassian Leaders to share what’s new, use case stories, solutions, and tips & tricks to advance the use of Jira for any team.
Join this virtual platform to network, learn new innovative ways of working, and meet like-minded Jira fellows.
👉👉👉 Use JEXO10 code for $10 off
Work Life, a brand new in-person and digital event
Exciting news for everyone in the US or traveling to the US in September. A new in-person Atlassian-organized event is here!
WorkLife is focusing on the evolution of teamwork, collaboration, and getting things done.
The meetup is happening on 29th September in San Francisco and is free to attend. And if you can't attend in person you can always join online!
Have a look at the event landing page to find speakers and the sessions and register!
Six ways we’re making Custom UI Bridge more powerful
For the article of the week, this week we have a write-up for developers. This article is talking about the latest features launched to Forge Custom UI Bridge.
Custom UI is the flexible way to build applications using the Forge app.
The other method is using Forge UI. Although considered more secure, it restricts your capabilities to existing components and functions created by the Forge team.
The Forge team has also launched extra upgrades
- Events API now allows various functions in your app to talk to each other by emitting and receiving events. For example, you can have two dashboard modules that listen to each other's updates and reflect the changes.
- Native alert flags now enable you to notify the user when they take action in your app.
- Modals - you can now have them bigger, occupying almost the entirety of the screen to help you have all the UI goodness you need.
And there's a couple more. Go through the article if you're interested.
Another important update here is that these changes will make it through to Forge UI Kit as well and it seems the team is making some important upgrades there as well with announcements planned in the next few quarters.
Forge is progressing fast, make sure you stay on top of these upgrades if you're a Marketplace Partner developing apps.
Because Forge is the future of how you build.