[#JRA-8230] CSV Importer does not respect Issue Security Schemes

JIRA

CSV Importer does not respect Issue Security Schemes

Created: 13/Oct/05 06:57 PM Updated: 30/Jul/06 07:34 PM

Component/s:

Import / Export

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Part

This issue incorporates:

JRA-7962 CSV importer should allow default values for missing fields

Participants:	Bettina Zucker, Brian Nguyen and Mark Chaimungkalanont [Atlassian]
Since last comment:	136 weeks, 2 days ago
Labels:

Description

« Hide

If you import data through CSV the default security level (if any) is not used.

Not being able to set the security level through CSV doesn't help either.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Bettina Zucker - 08/Dec/05 10:26 AM

I observed exactly the same problem on Version 3.3.3 enterprise.

My workaround will be to make a bulk change of security level on all freshly imported issues every time.

This is error prone and time consuming!

I see this as a security problem, since the lowest security level "None" is used when importing even if
the default security level in the jira Issue Security Scheme configuration is set to the highest possible,
as should be done in any reasonably secure system.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] - 08/Dec/05 09:00 PM

This solution to this is to implement JRA-7962. In that way the default value for the issue security field will then be respected