s_gridnevskii Rising Star

We would not need many service accounts if token defines access, e.g. has a role in a Jira project/space or is added to a confluence space instead of an account itself. E.g. Jira admin can create a service account with 5 tokens - one for project A, another for project B and so on. Project administrator then adds the…

ΟΚ but no todolist is needed in latter case. It can be done by editing description or last comment. ☐ complete phase 1 ☐ complete phase 2 ☐ complete phase 3 -> Edit description ☑ completed phase 1 ☐ complete phase 2 ☐ complete phase 3 Additionally I could set up automation rule that e.g. changes Summary when a subtask is…

@Celina yes you are right, but I used subtasks as action items and they work pretty well. E.g. we had test cases with subtasks as test steps. A QA tester opened the test case (work item), scrolled down to list of subtasks and followed steps. If any step failed he could open the subtask in a separate window and describe…

When we had datacenter I connected to Confluence using WebDav. I mounted pages to network disc and could work with them as files. It was pretty convenient since I could use standard linux tools like sed or grep to quickly modify pages.

I worked actively with Data Center and after migration to Cloud I noticed that atlassian-hosted Jira works almost 50% slower than self hosted solution on a cheap AWS server. In addition we have downtimes, not often, but they happen. We are on the other side of the globe and they prefer not to update Jira during USA working…

1. You may exclude subtasks from boards by using filter. 2. Work item has ... next to every subtask. One can click it and close subtask without opening it. 

I have a strange solution. Lets e.g. take into account "Time to resolution". In first column of SLA page set start to issue creation, in middle column pause on Open. This immediately starts SLA when issue is created and pauses it when it enters Open state. Now you can make request like "Time to resolution" < elapsed(1m)…

@Fabian Lim is it possible to skip check if custom field is empty? Something like Insight_Object_Attribute_name = ${customfield_ID} OR ${customfield_ID} IS EMPTY

BTW it would be nice if some kind of AI could convert incoming email with attached picture (or PDF) into a request with all fields filled according to what is on the picture. It will eliminate manual work. Maybe if invoice is within limits it can be paid automatically as well by a web call from automation rule to a payment…

Ι've been using it for a while for situations when vendors send proforma invoices and we block limits on cash accounts. After goods are received bookkeeper converts pro-forma request into a real invoice request using an URL created by automation in comment. No need to fill data again, just check if everything is correct.…

@Pablo first you generate a token in your profile (or generate a token for a service account). Then do a generic REST API call https://<your instance>.atlassian.net/rest/api/latest/issue/IT-2332 Provide headers Authentication: Bearer <your token> Content-Type: application/json If your request returns 400 then you can parse…

We use Jira REST API to create work items from HR system to Jira, e.g. Onboarding. But it is only one-way integration - after ticket is created work is done. We use two-way integration between CRM and jira. CRM can create issue in Jira using web call in automation and registers callback url in issue property. When…

Not sure if this is still relevant in 2026, but I just solved this mystery and it may help others. So the error is misleading in a way that the phrase is not correct. It should be something like "Jira could not create the issue since the value of one of the fields is missing or incorrect". How to fix. 1. Check fields on…

Rebekka Heilmann _viadee_, I was just guessing. In fact it is good to have service accounts for various automation rules. For the simple reason that if an employee retires all his rules will stop working instantly which will not happen if it is a service account that does all the work. I had this situation when previous…

Just a small sidenote. It is always better to use "latest" for REST API protocol version. It will work without changes in current, future and past versions of Jira. Instead of rest/api/3/status/idOrName better rest/api/latest/status/idOrName

Am I right that if I create an alternative GUI for my employees and vote if anyone wants to use it I can create service accounts for them and they can use Jira/confluence using alternative UI without paying to atlassian?

In addition to the abovementioned. 1. Use status colors properly. Blue means someone is working on item. Gray means it is on hold/paused/blocked. Green means item is done or canceled and no more work required. Usually green statuses have resolution. 2. Status names are nouns/adjectives. Transitions are nouns. E.g. a link…

Ιs atlassian going to publish Data Center under open source license? It would be good if community continues developing the product that the company decided to get rid of. Technically we have attlassian SDK, all we need to have is a license agreement that allows changing Jira source code and publish changes.

I think it is too dangerous to allow AI to make changes in config because some of them are irreversible. E.g. if a new workflow does not have some steps and you decide to rollback you will need to check history in each issue to find out what was the original status, make a temporary link in old workflow, transit issue and…

A rule of a thumb: never rename statuses. If someone wants to change status name create a new status, relink everything from old to new and delete old status. Status names are global. If you change in any workflow it will change in all workflows. I think Atlassian should make a warning there in the editor. BTW request…

@Julia Foden from what I see in original post contexts will not have projects field anymore. If their migration code is wise enough it will copy the custom field and assign each copy to different configurations. If migration code is stupid they will just drop all contexts for the field except one and your project CDE will…

@John Dunkelberg some time ago we were calculating the cost of Jira + Plugins and found out that it is much cheaper (for us) to have several instances. Simply because we have loosely coupled departments. Some people need plugin, some will never use it and we will pay for them. Seems like the same story. After changes we…

I don't like it. Admins used field contexts to hide fields users should not see, e.g. some data used in automation. It also added flexibility - e.g. if you even do not want a field in another space you could make it invisible for users and share field scheme between several spaces. I understand that you want to make it…

I guess they tested new UI with a focus group. Somewhere deep in the jungle of Bangalore to make it cheaper.

@Carolyn White I guess Severity is important only for team lead. Assignee (the one who fixes the problem) should not care about severity at all. He sorts his tasks by priority and fixes most important ones. Perhaps Severity should be present on issue creation screen, especially on service desk portal. After creation…

For the SLA - obviously you did not check them before applying 20 master workflows. I guess you also put arbitrary statuses when applying general workflows to issues and you will have more problems in series 3. I always take a project lead with me when I apply a general workflow and we sit together and set proper statuses…

I never understood why people have severity in addition to priority. If customer is in big trouble then save him as soon as possible - use priority Highest. In one company where I worked as a head of support I even had a red flag - when production failed I raised this flag on my monitor and everyone from QA to development…

FYI I tried postfunction Load issue data and it changed the summary to 1. And I could not delete this postfunction. I had to create new workflow :( Finally I created a transaction that starts from Open and ends on Open and I call it from automation rule. My version of automation for jira cannot extract data from forms, I…

Actually it is enough to add Html to the name of the method public String getPageVersion1Html() { return this.pageVersion1; } Of course you will need to use PageVersion1Html in template.

Google did it with Chrome and both versions coexist - Chrome and Chromium