Christian Czaia [Decadis AG] Expert

Hey, you're right in terms of reporting...Sorry that I can't help you out here...

Exactly. You can configure the links as you like.

Have you thought of issue links? That way you can keep a single issue and when it affects other products you just link them. I could think of a single "dependency" issue in every project that you could easily link to and which could provide an overview of all the dependant issues ferom other projects. Cheers Christian

You have to share the dashboards with the users. As soon as you create a dashboard you have the option to share it with people e.g. all, a specific group or a project. You as the created will need to have the "Create Shared Objects" global permission though...…

Hey, this is not a solution but the Misc Workflow Extensions plugin has the "hide transition" condition by default selectable from the UI: https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions Depending on your JIRA version it's free of charge:-) Cheers

Maybe you're looking at different fields... Sure you're talking about the fix version(s) field?

Do you have an actual question?

As far as I know, as long as you don't use the Greenhopper simplified workflow and you have your issues tied to a workflow you had defined previously, Greenhopper "respects" that workflow meaning that validators, post-functions etc. will stay valid...

Anything in your log files?

Hey, I have an internal group with those kind of users and simply don't grant them the "JIRA users" permission. https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions

If you've added new resolutions you can limit the ones you want to be displayed via workflow transition properties like: jira.field.resolution.include = 1,2,3,4,8 (IDs of the resolution) https://confluence.atlassian.com/display/AOD/Workflow+Properties Cheers Christian

Same question just the other way round: https://answers.atlassian.com/questions/23555/any-way-to-do-field-level-notifications

Have you thought of letting your customers create issues from e-mail via the JIRA mail handler? http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email

After these 45 days you can't download new product releases (released after your license expiry date). Also you will no longer be able to request support for your instance from support.atlassian.com or via email / phone. You can find more info here:…

You might want to look at Jamie's script runner plugin as he's got a built-in script that's probably doing what you'Re after: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-RenameaUserID

Have you tried entering a summary? :-) Maybe you have deleted this field from the create issue screen but the field is mandatory... Cheers

Probably because you only have system fields on your first tab. They are shown in that specific area right underneath your summary. Below that area you have your custom fields. Maybe add another custom field on your first tab and populate it. Now you shouls see two tabs...

Hey, of course you can have tabs: https://confluence.atlassian.com/display/JIRA/Defining+a+Screen Any custom fields (except 'Date' fields) that have been added to the 'View Issue' screen can be moved onto a separate tab. Note, this restriction only applies to the screen associated with the 'View Issue' operation. Cheers…

Hey, just guessing: Your first "tab" is the information you see when viewing an issue. As soon as you enter some data!! on the second tab it shows on the view issue page. As long as no data is entered on that tab it doesn't show... Maybe that's your problem? Cheers Christian

In JIRA, if you have more active users than allowed by your license it doesn't stop working but you can't create new issues anymore. JIRA doesn'T know the concept of "concurrent users". If a user is granted Application access (prio to JIRA 7 - JIRA Users global permission) the users uses up a license, no matter if is…

Hi, if I getting you right you can realize this via a post function in your workflow: http://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-postfunctions Assign to Reporter Assigns the issue to the user who created the issue. Cheers Christian

Hi, when I type exactly what you posted my Confluence doesn't seem to recognize it as a macro (because of the $). Anyway you could maybe use the "No format" macro. I'm using Confluence 4.0.3.

Have you tried "labels != "LTP" OR labels IS EMPTY" ?

Why don't you deactivate those user accounts? https://confluence.atlassian.com/display/JIRA/Managing+Users#ManagingUsers-Deactivatingauser That way they don't count against your license and you retain the information on those tickets... Cheers Christian

Why would you want to do that? I mean you would mess up your comment section. That's why you have an extra tab for worklogs I guess..

Workflows are generally stored in the jiraworkflows table / the DESCRIPTOR field. You might want to have a look at this table. SR additionally stores info in the propertytext table IIRC. Cheers

Thanks for the suggestions. As I'm the only one working on DEV I have already configured the project I'm working on to only send mail to me and I'm not touching the projects with pre-configured notifications :-)

That would be very nice indeed. Let's see what the future holds:-)

By the way I'm still the only one who has voted for the issue so come on guys...

Hey, are you using Conluence OnDemand? If not, you have to have the "Confluence administrator" global permission: https://confluence.atlassian.com/display/DOC/Global+Permissions+Overview Cheers Christian