s_gridnevskii Rising Star

It is very easy to document changes if you have a separate project for change requests. Then you just add key of change to description of a workflow or screen scheme of an item and you can track who asked for change and why.

Bookmarks to most importand settings in browser. I also configured shortcuts P: project name and I: issue key for search string in browser.

Don't buy plugins from guys above, they are paid per user and your boss will not be happy. You need some REST API, e.g. your_instance/REST/API/latest/search?jql=type=bug You will get issues you need in json format. Save them as json file and feed to any AI agent, e.g. Gemini. Prompt will be like I need to create a table.…

So how are standard fields called now? Work Fields?

@Becker_ Rene this is especially true if you work in an Agile team and you use sprints and boards. One of my teammates has filter with 20000 work items and his board is very very slow. And closing sprint can take 2-3 minutes.

I guess one should create a work item with Kimi Antonelli car engine failure at exact place on the track in Barcelona.

In fact we also manage access to Jira projects in JSM. But these requests are approved by project owners who can be people not directly related to Jira, e.g. department head. All projects are stored in assets database and we have separate requests to create a new project in Jira that automatically adds new project to…

We have same permission scheme for all projects which was agreed with management and security team. The scheme is roll-based. We have dedicated roles for project members, managers, project administrators and security. When a new project is created we do not add individual members there. Each role is assigned to a group. We…

So it is a kind of an Initiative in terms of Agile? I think it just duplicates existing functionality confusing existing users. Since it does not relate to Atlassian and does not relate to Project. In fact from what I see on screenshots it can be perfectly implemented as an Epic if atlassian agrees to add Stories to…

@Philipp Sendek _catworkx_ do you teach your students that MCP can easilly spam the server and consume all Jira memory? 

This sounds good until we start checking how it is implemented. If MCP is hosted separately from Jira and requests info using REST API it puts severe load on Jira instance and consumes your REST API rate limit which is low for cheap subscriptions. It would be nice if MCP worked directly on Jira database. I saw a couple of…

I don't think you need Rovo to answer these questions. Existing tools provide answers without heating up planet Earth and eating your tokens.

My success story is that I created a free Gemini account and got a token for API. When I receive email from customer into our Jira (ServiceDesk) automation rule calls Gemini REST API and I get proper values for fields. No tokens no extra loadon backend no nothing.

@Kelly Reddy our instance has 250k issues sorry workitems since 2015 and I think our Rovo tokens will fly away like sand between fingers. This is really a big problem and we all wait for explanation from Atlassian. I can understand their logic. Every request to jira backend consumes $$$ and agents generate hundreds of…

Funny. Why they use summary for asset instead of Label or Name? Anyway thanks, Julius.

Our company tries to be modern and started to use AI agents working with jira issues. Perhaps we will need to forget about them since every agent consumes many REST API calls. I understand Atlassian needs money since there is no oil in Australia and prices go high, but come on guys rest api call is very cheap in terms of…

I checked the WebResponseBody class in Java and indeed it is not a collection, it is inherited from Object. And toString() implementation looks weird. So looks like the only possible way to output "key": "value" in automation rule is to list all possible keys in automation rule (Dot notation). I tried to trick Jira into…

It provides invalid json text without " for field names and text values.

I tried, but it reports something like this { id: 2123123123, count: 22323, metadata: { value: fsdfsdfsd, other, title : some data }, lastSeen: 2026-22-11 sometextwithcommas: sdd, ff:, ssd, othertext: } If I decide to then split the string using commas I can run across fields like sometextwithcommas that contain commas and…

Hi @Darryl Lee Is it possible to convert webResponse.body into a dictionary so that I can use the following smart value code: {{#webResponse.body.asList}} "{{name}}": {{value}} {{//#}} I need it so that I can output whole body as json into comment without dot notation since I am not sure what can be value names. Something…

Another option is to make an intermediary status and automatically transition issue to destination status after rule does what is has to do.

@Mat hm, I always thought it is optional to link form fields with Jira fields. Did Atlassian change it recently? Then it is one more reason to stay in Data Center :)

For Service Management another option would be to use assets fields. They can easily be reused in many projects since its type is the same for any asset. Another great feature is that we can give service agents an opportunity to edit assets in a specific Schema and they can change options available on the field without…

Unfortunately assets are available only in expensive subscriptions. 5000 objects limitation is nothing. If it is not too late is it possible to have a calendar gadget showing assets close to expiry? E.g. I have a date attribute in object type and want to be aware of objects with this attribute set to current date. It is…

Actually we have 2 permission schemes. One is used for active projects, another is used for projects where no one can create issues. We have a strong security policy and we moved to same scheme for all gradually. Before that everyone had access to everything.

@Ananjan_miniOrange yes, it would be very convenient to add the same service account to all projects and have different tokens for each project. This way a user who has a token will be able to access only one project and not others. It will even be not too hard to implement from my point of view. Imagine user is an owner…

@Aron Gombas _Midori_ maybe one of triggers in git could take the text file with requirements from current branch and post it as a page in confluence. This way both developers and managers could have same document in two different places. Another option could be to involve AI agent to create tasks in Jira directly from…

@Aron Gombas _Midori_ perhaps some kind of a Readme in Gitlab that can be edited as normal source files and committed to repository with version tag. When someone downloads source code he will also download requirements to the same version. Jira version has a description field. Maybe putting there an URL to git repository…

I guess it can be done by rest api <server>/rest/api/latest/issue/<issuekey>?expand=changelog for datacenter and for cloud <server>/rest/api/latest/issue/<issuekey>/changelog Then we can ask gemini or any other neural network to get info from json and display in appropriate format.

We added Story work item to our projects. And use Epics to gather together stories. They both have very simple workflow - Open, In Progress, Done. In fact Epics and Stories are all that product managers need to plan their work. After project manager and team decides to take the Story into work they break it down to atomic…