a31181111baf - this issue has been fixed and is working for Jira Cloud instances, but if you continue to experience issues, please reach out to our support team who'll be able to assist you.

This issue still exists. I can't see the edit user properties option for users in Jira cloud instance @Rob Saunders

Closing this issue as it has long been resolved

I cannot disable the "jiraRedirectFilter"

Great if we can get this moved higher up in the backlog.

Thanks Atlassian!

Hi

I have also noticed that the workaround is no longer available since I cannot - disable the module.

Please assist since Tempo - requires me to activate the user property field for the timesheets to be valid as well.

Regards

Showkat

Any update. The workaround doesn't work for me, I can't disable the module but I need user properties

Hi ,
Our organization have been using User property block since we started creating tickets and we definitely need it as it one of the key field to store the user properties and plays a major role in contacting the concerned assignee. Could you please let us know when this field will be added to the User management option.

Please fix the issue as soon as possible.

Thanks & Regards,
Sriveni.

In response to Bernd (Helen's workaround), I have tried this workaround but it does not appear to work in the sense that in step 4 the "jiraRedirectFilter" does not have any option to "disable" it when hovering over the item (just states "Module cannot be modified").

I am using OnDemand version of JIRA v6.4-OD-02-003.

Am I missing something or is there another workaround for this workaround...?!

Like other people, this has affected the work in my company specifically the workflow which uses this info to create an important stamp during every create issue transition.
Would be "nice" if this feature was re-implemented as soon as possible.

Workaround was already provided by Helen Hung:
https://jira.atlassian.com/browse/AOD-7020?focusedCommentId=572139&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-572139

Is there a work around anyone knows? I have tried the CLI (which we use lots) and not been able to do anything meaningful. All I am trying to do is set the default user in a project role, so my workflow post actions work correctly.

We really really need this now. Why remove useful functionality??? we are using onDemand but getting a bit fed up with limitiations in this product.

Atlassian -
It's been 5 months since this functionality was removed. Do you have an estimate of when it will be added back for OnDemand customers?

I always appreciate your feedback martin.brueggemann, so thank you. You're right, this was not the best of our releases.

We are trying our very best to rectify the problems we've caused and also communicate where possible, to keep everyone, including yourself, informed of the impact of changes. As I've said before, we have learned a number of significant lessons with this release, and we're doing as much as we can immediately to start improving upon our execution and process.

Thank you for being so patient and passionate about our products.

Helen,
thanks again for following up on this.
Even though we already talked and so many messages were posted in Confluence and several tickets, I still think it's weird to have all the feedback and communication stuff after rolling out the new user mgmt. No rollback script. The train has already left, basically.

I guess "user management" was not a Story but an Epic, so there must have been several sprint planning sessions, reviews, demos...and not in a single one of them the user proxy flagged that crucial functionality would be dropped for weeks, maybe months?

My 2 cents...

Atlassian, any comments regarding this issue? Please, let us know what is going on ... your continuous feedback is imperative for this issue, because many companies has their processes based on this property field.

I really do not understand on which ground a company can remove functionality from a product without notifying customers in advance.
We use these properties to organise our processes in Jira. In other words: if I don't search for a solution (or hack), some of our processes are not usable any more for our company.

By the way: we are using a hosted environment of jira. I suppose that Atlassian could have made a simple query to check which users would be impacted with such a change?

Hi,

When this problem will be solved?

Property fields are necessary for our reporting requirements.

Please re-enable .

Regards

Showkat