Sergei Gridnevskii Rising Star

Jay has nice moustache but strange girl's voice :) You talking about security, but the speaker logged in with someone else's account to Jira to record a video. Maybe a minor issue but still an issue.

The more I think about it the clearer it is for me that the whole idea of Teams is artificial. And can be easily implemented using idea ONE PROJECT = ONE TEAM. E.g. business analytics and stakeholders have a Planning project that contains Epics only. They can move them in time, set priorities, have dashboards and graphs.…

So technically speaking Teams was a custom field and now it is a standard Jira field. Correct? Also it would be nice to add Teams as Customers to Service desk projects. E.g. Backend team as organization. This would help us not to bother about newcomers and those who left team in millions of places.

Agree. I even managed to parse XML from external server with graphic blocks. It was hard but possible.

I guess Atlassian has reasons for that. Nobody knows what you can put in scripts, like bitcoin mining, virus, something else. While graphic blocks are error prone and cannot crash Jira server.

Theoretically if you have a public hosting where you can run python or groovy scripts it is possible to expose a REST API and trigger it from Automation for Jira.

I guess business analytic should work on epics. Teams work on stories, tasks and bugs.

Another Team. We already have a bunch in Advanced Roadmaps.

I guess Atlassian should start from itself. Console in my browser is full of errors, service desk does not show objects at times. I need to start browser in Incognito to be able to work. Failed to load resource: net::ERR_BLOCKED_BY_CLIENT Failed to load resource: the server responded with a status of 409 () Failed to load…

After asking I figured out that I can add an ID attribute to Buckets, add ID column to Excel, autofill it with A3=A2+1 formula, make it an identifier in Import, perform an import and then delete ID attribute from object type. Looks like a workaround, but maybe Jira can do it an easier way?

Dreams, dreams. Most assets are text objects, we could easily store backups in Git and this will give us versioning. Sometimes auditors asked me what changed since last month and it could help me a lot. 

Assets are unstable in Brave browser - if one types an AQL and reenters same type after a while no objects are shown. In Chrome this bug is reproducible 50/50, only incognito mode helps. We created a help request for developers, nothing was done. Please fix bugs prior to adding new functionality.

He asked how to do that using Create Issue action. It is not a good idea to create hundreds of rules just for fun - both for the sake of observability and performance.

My Project Manager wants the Start date to be populated with current date whenever the issue is moved to In Progress state. He sees the Start Date on Plans page.

It works only if you delete users from Jira when they retire. It does not work if they were disabled.

Yes, same for me. If you forget/don't notice that a config is shared a minute after you make a change you have an angry team member from another team asking you to roll back changes. For me a rule of a thumb is to make a copy and make changes in a copy. Unless all teams agree that they need this change. P.S. One of the…

Another very useful tip. Create a project that would solely serve changes in Jira itself. For every config change requested by users create a Jira issue. Whenever possible describe the change with issue key. E.g. if you edit a workflow mark it with [ISSUE-223] in change description. It helps a lot to find who made a change…

I guess you were hit by a team managed project when you were young and you still remember it. I use them intensively for non-it teams like HRs, Reception, etc. It removed tones of workload for me - just show team member how to manage them and voila - they do what they want and do not bother you.

* Enable team managed projects for teams that know better than you what they need. Examples: HR, Business Management, Analytics. They are not IT guys, team managed is what they need. * Never add users and groups to projects permission schemes. Always use Roles. * Make custom fields as specific as you can. Avoid using same…

Don't be afraid, the sooner you start digging in the sooner you become a pro. I would suggest to start from a template, check how things are organized there, start using it and remove what is not needed step by step. After getting some experience you may create a blank project from scratch and move all requests from old…

Sorry my bad, I used wrong request type. Should be GET, not POST

@Dirk Ronsmans no, it does not. GUI is not the best but I can live with it. @Kristján Geir Mathiesen I think you can make 10 contexts for one field if you have 10 issue types in a project. 

1. Create a separate issue type for each request and use contexts for custom field - it works just fine. I use contexts for most of my custom fields and they are a real help.

Does not work for team managed software project

For the same case I use Automation for Jira and Create Issue Event. In Automation for Jira rule I check values of request fields and decide to what project to triage. After creating developer's project issue I link it to original issue with type Relates. When developer's ticket is resolved it triggers another rule that…

František it is much better now than it was 1 year ago. UX is terrible, but it works fast. JSM integration is good, Automation for Jira has API for Insight. I have not tried REST API yet, but am finishing 2 projects with Insight (Access rights Audit and Assets management) and so far so good.

I was expecting to read something terrible in the article because we use Insight intensively and some of the data we store there is critical. Thankfully they only changed name :) What I expect from atlassian is to make one button backup and restore for object type, maybe using git. We are currently using custom scripts for…

Same here - we had Freshdesk on L1 and mindless copypasting from Freshdesk to Jira software and back. Now we use Service Desk for 95% tickets and it is good both for clients (L1 support) and developers. We still copy some bugs to Software project but it is easily done automatically using automation rule and pattern in…

One more simple yet effective approach. User fills an important part of description right there on issue creation. Automation adds structure. User adds other sections after creation. One of our rules looks like this: h1. Business Requirements {{Description}} \\ \\ h1. General Flow \\ \\ h1. UI \\ \\ h1. Task Scope \\ \\…

Hail Carl III of course