This feature can be implemented by allowing permission shemes to be associated with issue types on per project basis. We are hoping to do this in a future version of JIRA. However, implementing this will be fairly labour intensive, so unfortunately I cannot provide any accurate delivery dates.

Thanks,
Anton

here

Hey Atlassian - on this site, if we try to create a Support Request, we are re-directed to a page telling us we can't (although Atlassian can move the issue to that type).

Support Requests are no longer handled by this system.

Maybe if you explain how you achieved this, the watchers of this issue could implement the same method, at least in part solving the problem.

This is a bit of a hack:

1. Create a Edit Message Custom Field
2. Add the Issue type to the context
3. Add the custom field to the create screen.
4. Change the default value of the custom field to something like:

   <div class="infoBox">
   Your message....
   </div>
   
   <script language="JavaScript"> 
   
   <!-- 
   
   function disableCreate()  
   
   { 
   
       var inps = document.getElementsByTagName('INPUT'); 
   
       for (i = 0; i < inps.length; i++)  
   
       { 
   
           if (inps[i].type == 'submit')  
   
           { 
   
               inps[i].style.display = 'none'; 
   
           } 
   
       } 
   
   } 
   
    
   if (location.pathname.indexOf("CreateIssue") != -1) {
       window.onload = disableCreate; 
   }
   
   //--> 
   
   </script>
   

This will disbale the button and display the box.

Cheers,
Nick

Hack or not, it's very kewl. Works great. I have a support project where clients can enter support requests and now I have a way of preventing them from creating Bugs, but still make it possible for us to change a Support Request to a Bug (the opposite of what you're doing on jira.atlassian).

we need this functionnality too.

any "delivery date" ? ( next year, next century ? )

cheers,
pierre-yves

Cheers,
Nick

I don't know if I understand your hack the right way.
I'v done everything like you mentioned, but now NOBODY can create this Issue Type ("change request" in my case). But I want to allow creating "change requests" to the group "business analysts".
If I wan't to disallow an Issue type for a project anyway, then I can configure this with the new feature you introduced a few month ago. So where is the advantage of you hack?

Marco

The hack is useful (to me anyway) in that even though no-one can create certain issue types for some projects, we can grant the "Move" permission to certain users that will allow only them to move the issue from one type to another.

It drives our BA's and development team crazy if everybody can create "his" change request!

Anyway, ovously there are still nothing I can do, except waiting for atlassion implementing this feature

Thanks for advance

<div class="infoBox">
Only business analysts can create change requests!
</div>

<script language="JavaScript">

<!--

function getElementsByClassName(strClass, strTag, objContElm) {
strTag = strTag || "*";
objContElm = objContElm || document;
var objColl = objContElm.getElementsByTagName(strTag);
if (!objColl.length && strTag == "*" && objContElm.all) objColl = objContElm.all;
var arr = new Array();
var delim = strClass.indexOf('|') != -1 ? '|' : ' ';
var arrClass = strClass.split(delim);
for (var i = 0, j = objColl.length; i < j; i++) {
var arrObjClass = objColl[i].className.split(' ');
if (delim == ' ' && arrClass.length > arrObjClass.length) continue;
var c = 0;
comparisonLoop:
for (var k = 0, l = arrObjClass.length; k < l; k++) {
for (var m = 0, n = arrClass.length; m < n; m++) {
if (arrClass[m] == arrObjClass[k]) c++;
if ((delim == '|' && c == 1) || (delim == ' ' && c == arrClass.length)) { arr.push(objColl[i]); break comparisonLoop; }
}
}
}
return arr;
}

function disableCreate()

{
var users = new Array ("john jonson", "Eric jonson", "marco simon", "Administrator" );

var myObjColl = getElementsByClassName("toptext", "font" );

var bolHide = 0;

for (i = 0; i < users.length;i++)
{
if ( myObjColl[0].innerText.indexOf(users[i]) != -1 )

}
if ( bolHide == 0 )
{
var inps = document.getElementsByTagName('INPUT');

for (i = 0; i < inps.length; i++)

{

if (inps[i].type == 'submit')

}
}

}

if (location.pathname.indexOf("CreateIssue") != -1) { window.onload = disableCreate; }

//-->

</script>

Cheers,
Nina Engels

Our process does not allow customers to create or view issues of certain issue types, either.
So, dear Atlassian team, please consider implementing this feature

Best regards,
Joey

I am trying to use the code sample that you have supplied at the above link. I have tried your below code and it does NOT seem to work. The create button is still active , when the info message is displayed. Do you specify individual users who have or do not have access into the issue type? What abouts groups ? Can i specify a group name instead of a user name?

You help would be greatly appreciated.

Regards,

Below is the sample code that i am trying to use. Is this code right or is it missing something??

<div class="infoBox">
Only business analysts can create change requests!
</div>
<script language="JavaScript">
<!--
function getElementsByClassName(strClass, strTag, objContElm) {
strTag = strTag || "*";
objContElm = objContElm || document;
var objColl = objContElm.getElementsByTagName(strTag);
if (!objColl.length && strTag == "*" && objContElm.all) objColl = objContElm.all;
var arr = new Array();
var delim = strClass.indexOf('|') != -1 ? '|' : ' ';
var arrClass = strClass.split(delim);
for (var i = 0, j = objColl.length; i < j; i++) {
var arrObjClass = objColl[i].className.split(' ');
if (delim == ' ' && arrClass.length > arrObjClass.length) continue;
var c = 0;
comparisonLoop:
for (var k = 0, l = arrObjClass.length; k < l; k++) {
for (var m = 0, n = arrClass.length; m < n; m++) {
if (arrClass[m] == arrObjClass[k]) c++;
if ((delim == '|' && c == 1) || (delim == ' ' && c == arrClass.length)) { arr.push(objColl[i]); break comparisonLoop; }
}
}
}
return arr;
}
function disableCreate()
{
var users = new Array ("john jonson", "Eric jonson", "marco simon", "Administrator" );
var myObjColl = getElementsByClassName("toptext", "font" );
var bolHide = 0;
for (i = 0; i < users.length;i++)
{
if ( myObjColl[0].innerText.indexOf(users[i]) != -1 )

}
if ( bolHide == 0 )
{
var inps = document.getElementsByTagName('INPUT');
for (i = 0; i < inps.length; i++)
{
if (inps[i].type == 'submit')

}
}
}
if (location.pathname.indexOf("CreateIssue") != -1) { window.onload = disableCreate; }
//-->
</script>

#if ($authcontext.user.inGroup('employees'))
##do nothing
#else

lines of code but it doesn't work. JIRA doesn't seem to execute just that portion of the code. The javascript works fine. Any ideas?

Are you using this type of custom field: "Velocity processed Message Custom Field (for edit)"?

Would like an implementation of this feature as well.

Have you considered the alternative of implementing conditions on the initial action in the workflow in the same way as conditions on all other actions in the workflow ?

or does this impact the OS workflow engine ?

Regards,

Erwin.

Thanks and Regards
Payal

25 Décembre 2050

I guess he is taking a LOOOONG vacation

Even our enterprise would be more happy to see this enhancement.
Meanwhile , as per Payal's question, please can you let us know where we have to add this snippet of code
to effect.

Thanks.

we need that also. We have a project where customers can submit feature request. But also within this project we have internal issue types we use for aggregation, clustering and version planning. Customers should not be able to create, edit & see issues with these issue types.

Thanks

regards,
Paul

Re the external customer issue - we would be happy for the ability to set permissions even on a version level that way you can open up a version for example 'Beta Testing' to an external client for viewing whilst keeping the rest of the project invisible to them. We have this problem quite a bit . Thanks, Jo