Christian Czaia [Decadis AG] Expert

Hey, you can select the screen that you want to be displayed for every transition. You can also chose "no screen for this transition" which is the first option in the list...

How would I remove them...Maybe you could point me to the right direction. Would that be close to what youre describing in your example Add or remove options to single or multi-select fields on your example page? https://jamieechlin.atlassian.net/wiki/display/JBHV/Miscellaneous+Behaviours+Examples

As your agile board is just a visual representation of you JIRA data I'm afraid you can't do that out of the box. Issues and sub-issues are seperate entities and their workflows aren't technically connected...

P.S. Ecourage your people to save their changes once in a while:-)

Hey, if they are editing different sections those changes should be merged automatically. It works with pages and blogs. http://confluence.atlassian.com/display/DOC/Concurrent+Editing+and+Merging+Changes Cheers Christian

Make sure those people have the "can use" global permission: https://confluence.atlassian.com/display/DOC/Global+Permissions+Overview Cheers Christian

Please, try to search before you post: https://answers.atlassian.com/questions/105352/how-can-i-restore-deleted-jira-tickets https://confluence.atlassian.com/display/JIRAKB/How+to+restore+accidentally+deleted+issue+in+JIRA https://answers.atlassian.com/questions/57259/how-to-restore-deleted-issue-in-jira…

Hey, I would try to work with the JIRA suite utilities plugin. You can create a post function on the create issue transition to update the custom field "epic link"... Cheers Christian

As far as I know you can't disable it via UI. It's the jira.webfragments.user.navigation.bar you're talking about I guess. Can be found in your systems plugin library (Bereiche der oberen Benutzernavigationsleiste).

MySQL and UTF-8

http://xzz.de:18081/svn/RepositoryZ/Sample_name_Ü_with_umlaut.docx Custom field yes. Same problem if I paste this link into a comment though... Link breaks right after the umlaut. I'm on JIRA 5.0.7 BTW

Got a point. So I guess Pam should check those requirements...

Can be... but Note: this report is only available if your JIRA administrator has enabled time-tracking and installed the JIRA Charting Plugin. https://confluence.atlassian.com/display/JIRA/Workload+Pie+Chart+Report

Have you enabled timetracking?

Or the role which has the "administer project" permission :-)

Try bulk-editing the security level...

When you say sometimes... may this be project related? I mean if you have a project with noc subtask issue types presen even the plugin can't create a subtask...I image you'Re using create on transition plugin?

project administrators can only assign people to roles, edit project versions and components. JIRA administrators (full JIRA access) on the other hand are divided into administrators and system administrators. See this doc for further explanations:…

Hi Taraka, the Tempo license must match your JIRA license. Cheers

Hi, you could create sort of a project template and copy it using the Script Runner Plugin https://plugins.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner Cheers Christian

Hey, the following query returns the projectrole, the group in that role and the project using that role: SELECT r.roletypeparameter, pr.name, p.pname as project FROM jira_prod.projectroleactor rleft outer join project p on r.pid = p.idleft outer join projectrole pr on r.projectroleid = pr.idwhere roletype =…

Well, you just have to create another screen without the external issue ID field and associate that screen to the view issue operation in your screen scheme... https://confluence.atlassian.com/display/JIRA/Associating+a+Screen+with+an+Issue+Operation Cheers Christian

Have you thought about creating an issue type called "milestone"? Associate a screen which only has sth. like a due date and the summary, maybe making it non-editable? Now you could link all the tasks with that milestone and you easily identify the issue by its type... Cheers

Look here: https://www.atlassian.com/software/jira/download-archives

Do you have the "jira-system-administrators" group in your production environment and / or are you part of it?

AFAIK the edit permission is the ground level permission. So people in your SPR Manager role can only edit the issue if they are either reporter, assignee or administrator...

Try: jira.permission.edit.projectrole = 10103 BTW @jobin, this is one of the most valuable pages for JIRA admins... Thx Jobin! ---- BTW: I'd put that property on every "final" workflow step (instead of jira.issue.editable = false / JIRA default) jira.permission.edit.group = jira-administrators That way an admin can still…

Out of curiosity, why don't you use the default issue links to link stories and test cases? That way you could easily use SR to search for those issues? Cheers

How about a cron job in Outlook :-)

Maybe the estimate fields are not present on the create issue screen associated with your stories?