You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hi,
We have created some insight field and we were very surprised when we see some object with a lot of issue.
This field has been set for one project. We saw we have a lot of connected jira issues on one object linked to this insight project. This connected issue are mainly from other projects in JIRA.
I don't see any log of default setting in audit log and activity.
Is there anyone with this kind of issue?
Thank you in advance for your help.
Regards,
Mickael.
I would recommend you to check the settings of your custom field - contexts and default value. Administration -> Issue -> Custom fields -> Your custom field -> Actions column -> Configurate
Would you please share a screenshot from this location?
The most common case is the context of the custom field is not limited and there's a default value set, which results in the situation, where all the new created issues have this field set up, even though the field in not present on the screen.
Hi @Hana Kučerová ,
I noticed that yesterday.
On this field, context was global and for all project. However, we didn't set default value.
It's look like linked to the global configuration.
Can you confirm it?
Regards,
Mickael O.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mickaël Orsolino ,
thank you. The field is global, but the default value is not set, so the custom field is probably not set during creation.
I recommend you to limit the context of the custom field, but still we need to find out, why there are so many connections.
If you try to look into the issues from the other projects and search through the History/Activity/Transitions tabs, are you able to get information, during which action the custom field was set?
Please, also check the screens for your custom field (Administration -> Issue -> Custom fields -> Your custom field -> Actions column -> Screens) - are these checked screens really only used in your project and not shared with other projects?
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI @Hana Kučerová ,
It's very weird because I don't see anything on the history/Activty tab on each ticket.
Its an example of impacted ticket on a test project:
For the concerned field, I have only two screen associated:
On this case, the field is still global. I think it's only linked to the context.
Regards,
Mickael O.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. Hmmm... this really indicates, that these issues are created with this value.
Please, just to be sure - check the usage of the two screens, which are associated with your custom field.
Then please, try to also look to the used workflow(s) in your other projects - are there any (Insight) post functions on the first (create) transition?
You can also check the Audit log (Administration -> System -> Audit log) and try to search for config changes on your custom field (maybe there's been some default value in the past?).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.