Head of Data Science and Analytics @ Atlassian | Leading data-driven strategies | Cricket Enthusiast
Learn about all the cool things we do through Automation
Automation just leveled up! ⚒️ Check out some of the new automation features added across the Atlassian suite. From natural language rule-building with Atlassian Intelligence, to more admin controls – there’s something for every team to love. Read more on the blog: https://go.atlss.in/6fna87
The #NaturalLanguage #RuleBuilding with #Atlassian Intelligence and enhanced admin controls are fantastic features to streamline #workflows and empower teams. Discover more: https://lnkd.in/g5yc9AHq Connect with us: https://lnkd.in/gCJDebt8 #3RInfotech #Atlassian #Jira #Confluence #JiraServiceManagement
Automation just leveled up! ⚒️ Check out some of the new automation features added across the Atlassian suite. From natural language rule-building with Atlassian Intelligence, to more admin controls – there’s something for every team to love. Read more on the blog: https://go.atlss.in/6fna87
Automation just leveled up! ⚒️ Check out some of the new automation features added across the Atlassian suite. From natural language rule-building with Atlassian Intelligence, to more admin controls – there’s something for every team to love. Read more on the blog: https://go.atlss.in/6fna87
Hello again Atlassian community, on today's Community questions, we answer Fahad Akhtar's question on "How to retrieve REST field parameters?" So, Fahad Akhtar's issue is with REST API failure for ticket input. Recently changed fields seem to be causing a hiccup, preventing the seamless creation of new tickets from the Company A end. This appears to be a field mapping issue. It's likely that when the fields in Jira were updated, the old field parameters were replaced by new ones without also updating them on Company A end. In Jira, Field ID remains same but the names could be changed hence causing an issue. The REST API defect field uses the Field ID to map the values. Here's what we suggest 🚀: 1. Open one of the previous tickets created successfully via REST. Choose the option "export to JSON" in the
Hello again Atlassian community, we have a great discussion today regarding a question titled "Re: Re: Send Notification when Total Billable Project Tim..." from our user Mayra Hernandez. Mayra is looking for a way to get notified when they have reached 80% or 90% of the total billable time for a project within a current month, this time includes many issues. This can be achieved by creating a custom field that tracks the total time spent on the issues for a project in a given month. You can then create an automation rule that triggers a notification when the value of this field reaches 80 or 90%. In the issue navigator, you can search for the issues using the JQL query "project in
Feeling like the first day back after a long weekend? 😴 We've got some prompts to help with knocking out today's to-do list: ✅ Summarize messages in [#Slack CHANNEL] ✅ Summarize the resolution for all Atlassian Jira] tickets that mentioned [CUSTOMER] in the past week ✅ Who can help me with debugging: [ERROR MESSAGE] ✅ Suggest how to resolve this problem reported by a customer: [CUSTOMER MESSAGE]
Great migration insights today, including input from the legendary Phill F. ! There's so much focus on the business value that can be achieved with Atlassian tools, ScriptRunner and #ScriptrunnerConnect!
Atlassian Engineer @ TX Services | Atlassian Community Leader | Atlassian Creator | Product Owner
👍 It's true, you can use improve issue feature that is powered by Atlassian intelligence. What does it do? ☑️ Helps with writing better issue descriptions ☑️ Helps with summarizing the comments ☑️ Generates subtasks based on the issue description #AtlassianCreator #Jira #AtlassianIntelligence