Christian Czaia [Decadis AG] Expert

You just have to be aware that those "users" will show up as possible hits when you are using the auto-complete feature of the JQL search...

Check this question: https://answers.atlassian.com/questions/52111/how-can-i-configure-my-notification-settings-so-that-people-aren-t-notified-by-their-own-actions You should deactivate the option mentioned there in your global settings. Nevertheless, this doesn't change current user seetings.

@Nic Brough I was looking for older posts but my search for the "enterprise" tag didn't produce the question you mentioned above. Sorry for the duplicate..

That's what I have now but regarding https://answers.atlassian.com/questions/49613/jira-5-1-inline-editing-how-this-will-work-for-you there is a chance that the plugin won't be maintained in the future

Hey Radu, I'm currently evaluating the WF sharing plugin (JIRA 5.0.6) but until now I didn't get it to work. I'll keep trying:-) My problem is that I don't need those validators (and updaters) as part of a workflow transition. I need them to execute in real-time...

Hey Radu, you're right. Changed the title and deleted the intro...(could have been the title of a "Daily Sun" article:-)) It wasn't my intention to scare people but I wanted to know if others are facing similar problems. I mean you see people commenting on regular Atlassian documentation pages, but not that much. I'd be…

Hi, check out this document: https://confluence.atlassian.com/servicedesk/configuring-request-types-and-workflows-457704356.html Customizing request type fields In Settings > Request types, select Edit Fields next to the request type you wish to edit. The fields and descriptions that appear in a request type are based on…

True. I was mixing things up. I just read " an additional status "Reviewed", which "Open" issues must be transitioned to before being assigned to partners" believing that the transition would be between OPEN and ASSIGN TO PARTNER. Should have read the title more carefully...

Maybe you could have two transitions and restrict the one going directly into "Open" to users in a specific role using conditions...# Cheers Christian

Try restarting your server. Sometimes changes get reflected once you transition to another status... Try that aswell

Hey, remember that you're talking about two things. The status and the step. When you view your workflow you only see the name of the step (which is associated with a status). On the view issue screen you see the status, not the step. Hope that helps, Cheers Christian

Hey, if you go to the sprint report page and select "sprint report" you get a list of all the issues. On that page you have the "View in Issue Navigator" link which gives you a list of all the issue in a sprint

https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue#WatchingandVotingonanIssue-Issuewatching

Funny thing, have you tried entering the same question in Google? Leads me to the documentation posted here :-)

Definitely check the docs posted by the others... but answering your question: Yes, it is possible :-)

Now it doesn't make sense anymore since my answer pops up above yours 

It's me

Jamie's script runner is what I would go for so I guess you hit the spot. I guess you have to do dome scripting since you're looking for a substring. Other than that you could have a look at this plugin : https://marketplace.atlassian.com/plugins/com.fca.jira.plugins.workflowToolbox.workflow-toolbox Cheers

I've done it that way. Works like a charm...

AS to my knowledge reposiories are only limited in Fisheye

Like with most Atlassian products, the only limitation is the active user count.

Check this guideline: https://confluence.atlassian.com/display/ATLAS/Scaling+JIRA Cheers Christian

I would make "story" the default issue type in your project (issue type scheme). That way it works for me...

Re-index and server restart

A server restart did the trick...

The base URL is correct and working well with e.g. application links...No proxies... I'll raise a ticket but thanks anyway

Sorry. I got it wrong:-) Could you try: Readonly except current user is reporter? I guess you made sure that you're the reporter, right? ;-)

I think you got it the wrong way. Waht I see is: "Make field Readonly when Current User is Reporter" I would change it to "writable when current user is reporter" OR "readonly EXCEPT current user is reporter" Cheers

With JIRA Agile 6.3 you can edit Epic links directly in JIRA: https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3+Release+Notes#JIRAAgile6.3ReleaseNotes-EpicsandSprintsarenowfirst-classcitizensofJIRA

Do you have the "Epic Link" Field on your edit issue screen? (And you'd have to be using JIRA Agile, not the old Greenhopper)