Christian Czaia [Decadis AG] Expert

Maybe you have custom headings defined that are not being recognized? Have you tried importing a doc with the standard headings?

Take a look a the blueprints packs on the marketplace... https://marketplace.atlassian.com/plugins/app/confluence/featured?category=Blueprints Cheers Christian

Hey, I'm not entirely sure but you're iterating through the entire ABC project 3 times!!! Maybe try to limit the ABC project to sth. like: issueFunction in hasLinkType(.....) to reduce the number of issues in your ABC project. Cheers Christian

We're currently evaluation this plugin and it seems to fullfill our needs: https://eazybi.com/help/jira-plugin Cheers Christian

Do you have project administrator rights?

Well, it seems like you haven't configured the workflow correctly. Seems like you don't have any transitions configured after the open state. Check the documentation: https://confluence.atlassian.com/display/JIRA/Configuring+Workflow Cheers

As far as I can see the order of the dropdown in your create issue screen reflects the order given in your issue type scheme... What do you mean by oroject screens? A filter gadget? I would guess those are ordered by the issue type ID...

I'm afraid this won't be possible. There is a translation page where BTF customers can download custom language packs but they are not applicable for cCloud instances. For more information please refer to: https://confluence.atlassian.com/cloud/languages-744721667.html Cheers

Check the "assignable user" permission aswell since if the user isn't part of that group the "assign to me" function will not be enabled..

Check https://jira.atlassian.com/browse/GHS-10687

Hav you set the correct date format during the import? In your case it should be: dd-MM-yyyy

Check if you'Re using the behaviours plugin as it disables the inline-edit functionality of issues with behaviours attached to them...

Hey, what error?

Why don't you use the "bulk edit" operation?

Gabriella is right. One thing to consider, if you're using an older version of JIRA before Atlassian introduced the "Transition issues" permission: Make sure that transitions can't be triggered! Again, just relates to older versions but in these cases you had to add conditions on all transitions because even if people just…

Atlassian considers this to be an "improvement" :-) but apparently they are working on it...

Yes you can, in the project admin section in JIRA under the versions tab you can manually release versions...

Your board is based on a filter. Add sth like. AND fixVersion IN unreleasedVersions() and you won't see those issues after releasing a version.

Couldn't you just use a single security level and add the reporter and lets say the project role "Users / or members". Then you could make the security level the default level in which case users wouldn't have to set the security level manually? Cheers

Try this (with asterisk *) Project = DEMO and Status = Open and Priority = Critical and summary ~ “UNIT- 456*” Cheers

I don't really get your problem. You simply have to add the "assignee" filed to the screen that's associated with the particular create issue operation in your screen scheme. When you se the assignee field you can pick the desired assignee. It will only be assigned to the project / component lead (or unassigned) if the…

I'm not entirely sure but I think the Agile tab still refers to the classic boards since the project can't really know which SCRUM board you are using...

Are you asking if you can just purchase "additional 100 licenses" on top of your 500? I'm afraid that's not possible. If you want more than 500 users on your system I guess you will have to get the bigger license ...

FixVersion != "IceBox" or FixVersion IS EMPTY

Hi Emil, thanks for the response. It was my fault this time. I tried to highlight the text in editor mode:-) So it's definitively not you plugin. Cheers Christian

You can bulk assign issues. Your problem is (that's my guess) that closed issues can't be edited. At least that's the default (jira-workflow). You'd have to make them editable again by deleting the property on the closed step: jira.issue.editable=false

A board is just a visual level on top of you JIRA issues so you have to look at them: Maybe you could create a custom field (flag) that only certain people can set (you could use a transition with the same target step for example) and put a condition on all the transitions leading to whatever statuses (steps) are mapped to…

I was having problems with the flash based editor. Try the text based editor, there you should be able to change the destination step..

Hey Anton, just installed the latest Greenhopper in combination with JIRA 5.2.11 and it seems that the translations I found to be very disturbing (see original question) made it into the product. Sorry, but that's something you really should be investigation... Make a survey for German customers and ask them what their…

Hey Anton, the overall quality of the German translations in JIRA has improved over the last couple of releases. At least as far as I can tell. Talk to you soon. Cheers Christian