In our configuration we have: Several projects that shared: flows, customfields and behaviour definitions. Sometimes, when users edit an issue several customfield are cleared in a random way. When it happens: * The customfield modified by users is not always the same. * The user that modifies is not always the same. * The issuetype which losts information is not always the same. * Not all the information is losts every time. * Not the same information is lost every time. Somebody has any idea about which could be the reason of this behaviour? Is a connection problem? Is a presentation layer problem?......

This question is a bit meandering. Are you able to reproduce a problem with a simple behaviour? If so can you post it. When you disable behaviours the problem goes away? What are the versions of jira and the plugin?

That's a bit of a problem. When I broke it, the "things" were me being inconsistent in my approach, not thinking it through or even just failing to understand how it was working. If you've made mistakes, they're probably different ones to the ones I made, and I don't know what you've done with it. Hence the suggestion to simply turn it off to begin with. Then you can turn it on and try removing one configuration at a time, or the other approach - turn it on, remove all the config, then add it back one piece at a time until it breaks. (That's assuming it is the Behaviours you've configured, which we don't really know yet)

What kind of "things" have I look for to see where are the bad or mis-configurations? Jira will tell me any clue?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why sometimes customfields values are cleared when editing an issue?

Begoña Bonet

In our configuration we have:

Several projects that shared: flows, customfields and behaviour definitions.

Sometimes, when users edit an issue several customfield are cleared in a random way.

When it happens:

The customfield modified by users is not always the same.
The user that modifies is not always the same.
The issuetype which losts information is not always the same.
Not all the information is losts every time.
Not the same information is lost every time.

Somebody has any idea about which could be the reason of this behaviour? Is a connection problem? Is a presentation layer problem?......

Accepted answers

All comments

Joe Pitt

Have you tried re-indexing? Sometimes that will fix odd behavior. Otherwise I suggest opening a issue with Atlassian support.

Begoña Bonet

At this moment JIRA doesn't inform to me that re-indexing is needed. Do you mean that I must to reindex anyway?

Nic Brough -Adaptavist-

Yes, he does. Re-indexing fixes a broken index, and that's what Joe is suggesting has happened

Nic Brough -Adaptavist-

I wouldn't expect that sort of error unless

you've got a plugin that is affecting what happens on-screen
you've created listeners that do odd things
you've used javascript to try to be clever

My instinct is to do things in this order. One at a time until you find a step that fixes the problem

Re-index, as Joe says
Check the list of listeners for anything that might be doing it,
Remove any javascript you've written.
Then remove all the behaviours stuff and see if the problem goes away. If it does, then you know you've got something wrong in your behaviours definitions.

Begoña Bonet

Thanks, I'll follow your advices step by step. I hope to find as soon as possible!!

I'll tell you the results.

Begoña Bonet

In step 4 do you refer to behaviours defined using Behaviour Plugin? Do you? We are using 0.5.10 version.

Nic Brough -Adaptavist-

Yes, I do mean disabling the behaviours defined by the plugin. It's a good solid plugin, but sometimes people use it to do clever things and get it wrong. Before we can say that this is any form of Jira bug, we need to rule out that as a possible cause of the problem.

JamieA

Cheers Nic. Note there was a problem where the value of checkbox fields could be cleared if there was a behaviour on them, but that was the only field with that problem. That's fixed in 3.0.x of Script Runner (the plugins have been merged).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

behaviours