Why is Resolution Date set on Unresolved Issues after a CSV import
Usage FAQ
- 'Road Map', 'Change Log ', and 'Versions' Project Tabs Are Not Visible
- Allow editing of Closed Issues
- Allowing users to create issues anonymously
- Anonymising JIRA Data
- Appending Email Addresses to Comments Made by Anonymous Users when Using a Mail Handler
- Asking for an attachment on the Create Issue page
- Can I store customer details, like company, address and contact information, in JIRA?
- Changing Custom Field Types
- Changing Templates Used by Export to Excel from the Issue Navigator
- Changing the default session timeout
- Changing the Default Tab Panel from Comments to All
- Changing the Due Date Input Format
- Changing the Project Key
- Changing the Size of the Fix Versions and Affects Versions Select List
- Changing the Size of the Text Area Custom Field
- Changing the Temporary Directory
- Configuring project specific security
- Connecting to SSL services
- Current Reporter Browse Project Permission
- CVS ssh Jira Integration
- Displaying a Field Based on Another Field Selection
- Editing a custom field option
- Field Layout Schemes in JIRA 3.x
- Fields Allowing Custom HTML or JavaScript
- Finding the Id for Issue Types
- How can I control the editing of issue fields via workflow?
- How do I assign issues to multiple users
- How do I disable Firebug for JIRA?
- How Do I Use an SSL Certificate Generated Using openssl?
- How to change Multi Select Custom field size using script
- How to change the location of stdout and stderr logs
- How to clear the resolution field when the issue is reopened
- How to configure comment field to become mandatory in workflow transition
- How to convert types using Jelly
- How to deactivate comments for closed issues
- How to display a different format for the Number customfield
- How to ensure the Road Map tab is visible
- How to Get Unicode 'non-ASCII' Characters in HTTPS URL to Appear Correctly
- How to have long component version names display properly in the Issue Navigator
- How to re-order statuses
- How to re-order the list of issue operation in an issue
- How to resize the 'Components' and 'Affects Versions' fields in the Issue Navigator
- How to Restrict the Subversion Commits Tab to Selected Projects or Users
- How To Send Notifications By Issue Type
- How to show a transition only when the Assignee is different from the Current User
- How to update custom field values during workflow transition.
- Letting customers only create issues
- Login problems
- Mail error - Unable to relay
- Making JIRA login case insensitive for JIRA 3.13.x
- Parsing utf-7 emails
- QuickSearch guesses the issue key prefix (sometimes)
- Receiving Notification for Select Issues or Updates
- Removing Commas for Values Held in Number Field Custom Field Type
- Removing invalid characters from XML backups
- Removing NONE from the Issue Security Drop-Down List
- Re-order workflow transactions
- Resolved issues appearing in Open issues filters
- Retrieving the JIRA Administrator
- Sending JIRA Data to Support
- Setting Additional Fields for Issues Created from Email
- Setting a Default Value in the Description Field
- Setting Priority field value based on customfield value
- Showing Extended Timestamp in the Created Column of the Issue Navigator
- Tracking the Time Taken for Each Workflow Transition
- Troubleshooting Issue Creation Via Email
- Using JIRA to Manage reusable modules
- Where are the application server logs?
- XML format for import & export files
- How to Enable the FishEye Plugin from the Plugin Administration Screen
- How to Change the Number of Rows Allowed in the Text Type Custom Field Renderer
- How to Make a Federated JIRA Instance
- How to Remove 'Unknown' Option from 'Component' and 'Fix Versions'
- Automatic Escalation of issues
- How to Activate Header Row for Subtask List in Issue Detail View
- How to Limit the Number of Characters Entered in a Summary Field
- JIRA's Timestamp Doesn't Match the System Time
- How to Remove Duplicate Entries for Names and Groups
- How to Export Users to CSV from JIRA
- How Come JIRA does Not Show Direct SQL Data Modifications
- How to get JIRA Pages to Render when URL Contains an Underscore
- How to disable or enable the GOT FEEDBACK button
- How do I reduce my user count in JIRA
- How to Bulk Edit Groups in JIRA
- How to enable "Attach Screenshot" on Linux Machine
- How to Configure Workflow to allow Certain Group to Perform Certain Workflow Transition
- How to Create a FishEye's Changeset or Crucible's Review Link on JIRA's Comment or Description
- How to make the 'Assignee' field required when 'Allow unassigned issues' is turn ON in General Configuration?
- How to allow users to view sub-task only but not its parent issue
- How to change the Date Time Range Picker format to 24h format
- What if you wish your Custom Field Appearing in Issue Navigator but not willing to set the context to All issue types
- Why Fix/Affected Version sort differently in issue screen after picking more than one version?
- Modify the gadget limit on a dashboard
- How to add comments to Excel export
- How to change the Original Step in Workflow Transition
- How to Hide the "Configure Fields" Button on the Create Issue Screen
- How to display the issue type name in issue navigator column beside the image icon
- How to Edit Bundled or System Plugins
- How to auto disable compatibility mode in Internet Explorer
- How to restore a single attachment to an issue
- JIRA does not pick up the data after running an UPDATE or DELETE SQL statement
- Why is Resolution Date set on Unresolved Issues after a CSV import
- How to Set Monday as First Day of Week in Date Picker Calendar
On this page
Related content
- No related content found
If you import issues and map with "Unresolved" resolution field, it would cause this problem to happen. Basically after mapping the resolution field, JIRA will recognize the resolution field as Resolved before (even if you put "Unresolved" in the Resolution). For more information, read Defining 'Resolution' Field Values article as quoted:
Any issue that has the Resolution field set is treated by JIRA as "resolved". The Issue Navigator displays Unresolved when no resolution is set for an issue. So adding a resolution named Unresolved and setting it in an issue will mean that the issue is seen by JIRA as resolved. This will lead to confusion and is not recommended.
In the end JIRA will recognize the resolution date as the current date and time. For example:
So, what is the workaround for that?
Please try the workaround as per How to clear the resolution field when the issue is reopened article and do a Modifying Multiple ('Bulk') Issues .
Last modified on Dec 16, 2013
Related content
- No related content found
Powered by Confluence and Scroll Viewport.