Ignacio Pulgar Expert

Are you using a custom field? How did you enter the date exactly: by using your keyboard or by selecting it on a calendar?

You should open a request here: https://getsupport.atlassian.com/servicedesk/customer/portal/2

Exactly! I should have included how to easily navigate to the option. Regards!

Just change it from this URL: https://praveenbalineni.atlassian.net/secure/project/EditProjectLeadAndDefaultAssignee!default.jspa?pid=10300

Look at the second sympthom from your link. It might be the cause of the weird results of your JQL. If you need help on that, send me an email to ignacio.pulgar at incentro dot com. De nada! After all, you found the solution!

Great! Then it was about adding the post function to clear the resolución. Cool and good to know. If that ever happens on our instance, I now know where to look at. Thanks!

Remember you can make a closed issue editable by setting the workflow status Closed with the property jira.issue.editable=true

Forgot to say that you should publish the draft after editing your workflow. Have a look at the properties of statuses and transitions on the workflow and look for anything that denies edit/vote permission. You might want to delete such a property. And don't forget to publish the draft of your workflow. Otherwise your…

A workaround might be allowing to edit already Closed issues:https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html

Probably, it has something to do with the project permissions being different for both users.Look at https://<YOURS>.atlassian.net/plugins/servlet/project-config/<PROJECT-KEY>/permissionsPay special attention to the permissions that might have something to do with this:* Browse projects* Edit issues* Resolve issues*…

Could you tell who is being granted the View voters & watchers permission?https://<YOURS>.atlassian.net/plugins/servlet/project-config/<PROJECT-KEY>/permissions

Press the dot sign '.' and start writing 'general configuration' to quickly access those options.

Could you review these JIRA options?: Allow users to vote on issues AND Allow users to watch issueshttps://confluence.atlassian.com/jira/configuring-jira-options-185729544.html#ConfiguringJIRAOptions-options

Looking forward to know if it fixes your issue :)

Never happened to me, but for your description, I would think of the following hypothesis: The transition from Closed to New is not correctly set to fire a 'Issue Reopened' event. Follow these steps: * go to the workflow's diagram view and click on Edit * click on the arrow (transition) which goes from Closed to New * on…

Edit the workflow and add the :Resolve issue screen' to the transitions that go to Done.

A newer version of the addon has substituted the one. Look for Time Reports in the Atlassian's Marketplace.

Bump?

Voted for it! 

That would also a preferable default behaviour for us. Have just added the addon-timereports label, but this question would be better addressed by opening a suggestion into the addon's project page: https://bitbucket.org/azhdanov/jiratimesheet/issues?status=new&status=open Just click on 'Create issue' from the top-right…

As the built-in behaviour, you cannot see other users recently viewed pages. Nevertheless, if you are a site administrator (typically by being member of the group 'site-admins') you can login as other users as if you were using their accounts. That's done through the 'Login as user' button displayed at the top-right corner…

@Lukas Korenacka Have you already found out how to do what you wanted to do?

If you are not the current assignee of some of the issues, the operator that you need is WAS. Try this: assignee WAS currentUser()

+1 to your feature request, then 

Why would you want to remove this important warning? If people are not aware of that fact, that may cause loss of information by overwriting data...

Users can select the version from a dropdown menu once the Affects Version field is added in the basic view of the issue navigator this way: affects-version.jpg If multiple users need to be able to change the version, then the solution is a bit more complex, as only the filter's owner can edit the filter's query. For…

What you can do is: * save a filter like the one I suggested and edit the <your additional conditions> * set the newly created filter into the gadgets you want After that, you will be able to edit the new filter with additional conditions so that your gadgets are updated accordingly. Should you not need to add any more…

As you use Cloud, that specific plugin is not available to you, because it is only available for Server. The free option you have at your disposal is using a JQL like: <Your additional conditions> AND filter = <referenced filter name or filter id> In example: affectedVersion = 1.0 AND project = FOO AND filter = "The issues…

You may better report a problem at Atlassian Support: https://support.atlassian.com/servicedesk/customer/portal/23 If you include your browser's console log, it might be helpful for determining what's going on.

What Peter has answered is correct. There's also a new alternative to moving incomplete issues to a new sprint, which might fit better your needs for those cases in which you have already been working and have advanced in the resolution of an issue, despite of not having been able to finish it on time. The new option is…