Christian Czaia [Decadis AG] Expert

HEy, you can filter for timeSpent: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-TimeSpent e.g. timeSpent !=0 Cheers Christian

Maybe off-topic but you should vote for this issue that has been around for 10 years: https://jira.atlassian.com/browse/JRA-1973

@Nic isnt't the changed function restricted to some system fields (like priority, status?). The JIRA Misc custom fields plugin records the transition caller field if that's of any help: https://marketplace.atlassian.com/plugins/com.innovalog.jmcf.jira-misc-custom-fields

Hi, I'm afraid you can't. There are some special fields like assignee and status that will accept historical values (status change to.... after...) but priority isn't one of them. Cheers

The user doesn't even see the project under the projects tab? Are you using issue security levels?

They have to have the browse project permission in order to see a particular project

No problem:-)Trying to revoke my down vote...

Sorry but that's not right. As Janet outlined you can chage the issue type but the issue type has to have the same field config (workflow...) and the issue type has to be present as a field on the edit screen... Cheers Christian

HEy, what do you mean with "in edit mode"? You don't have the option "create subtask" in your issue operations tab (more actions) when viewing an issue? Cheers Christian

Hey, it's a condition associated with the start progress transition. Just the current assignee can do the transition... Cheers Christian

Have you tried re-indexing?

HEy, get a plugin like Jamie's script runner which extends the standard JQL: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions Cheers Christian

It should be sth. like jira.issue.editable or jira.permission.edit.group Cheers

Many reasons To restrict the editing of certain fields to only a specific project role (using conditions and a specific screen on the transition) , scripted calculations (using post-functions), setting field values / flags (post-function)... Cheers

No, it's called a global transition (marked as -->ALL in your workflow). Since it most probably triggers the Generic event in the workflow post-function you receive emails. You are probably using a simplified workflow, designed for Agile boards. If you are on a board you can't transition issues to to same status they are…

I doubt anyone can help you if you don't offer any details...

Actually I'm not sure how this is being handled now but some time ago you had to open up the space to anyone (well, or a group the desired user is part of) and restrict all the other pages. In your case you'd have to restrict parent 1 and parent 3. I would guess that you'd have to open parent 2, since this page has to be…

Simply reorder the version by dragging and dropping in the versions panel of your project admin page. Cheers

You could link the relevant Confluence pages to JIRA issues. I don't know how many docs you have associated with a single page though. You might want to check these links: http://blogs.atlassian.com/2012/02/link-jira-issues-to-confluence-pages-automatically/…

I doubt you'll get any answers to that... Please specify your question

Maybe try to use Script runner and execute a scripted JQL function. At least I made it work for a version field: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-issueFieldMatch(subquery,fieldname,regexp) Cheers Christian

Hey, not entirely sure but there was a similar question about the share butte in Confluence a while ago: https://confluence.atlassian.com/display/DOC/Customising+the+eMail+Templates That was the answer: You can find the template of "Share" emails in the Share plugin itself which is located at…

Why would you want to do that? Use a project role. You're far more flexible :-)

I guess you're referring to the classic boards in Greenhopper?? You should read this: https://confluence.atlassian.com/display/GH/The+Future+of+GreenHopper It states that the classic boards will be supported at least until November 30, 2013.

There doesn't exist an owner. What do mean by that? The reporter is the one creating an issue, the assignee is currently working on the issue... What else do you need? Cheerc Christian

I'd suggest writing a VBA macro. It should be pretty easy importing the filters into seperate XLS files (adressing the filter URL) and combining them to a single sheet (Assuming that the filter names don't change)...

If I get you right you want to limit the potential assignees, is that correct? If so you can achieve taht via project permissions: Look at the "assignable user" persmission: https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions cheers Christian

You'll have to set a context. That way only fields associated to aproject via the context will be shown: https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field Cheers Christian

I guess I've sorted it out with the help of Jamies comments: https://studio.plugins.atlassian.com/browse/JBHV-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#issue-tabs import com.atlassian.jira.ComponentManagerdef issueId = formContents["id"]def issue =…

I'm not sure why but all of a sudden it works...