Christian Czaia [Decadis AG] Expert

Maybe it's the delay (interval) of the Mail Queue Service . Maybe you could check that out... Cheers Christian

Have you tried turning it off and on again :-) I mean, are both processes running?

I guess that this won't be possible since JQL only represents the WHERE clause of a query. You'd need a SUM operation and a GROUP BY I guess... Cheers Christian

https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira/versions

We need the exception, not the task...

Hey, even if I can't help you others might... but I doubt that they will be able to help if you don't provide details about the exception (log excerpt) Cheers Christian

Just to make sure: You (or any other admin) haven't added any JS into a field description, a plugin or the announcement banner that could be causing this behavior?

Hav a look at this question: https://answers.atlassian.com/questions/140012/is-it-possible-to-reset-the-issue-key-number Cheers

that's an OR not an AND :-) That search would return all issues with either A or B as a label

labels = A AND labels = B

Yes, create a filter, include issue types that you want to include and use the filter in the gadget. sth. like "project = XYZ AND type in (bug, improvement)" Cheers, Christain

I'd also go for issue security levels. You can bulk restrict all issues and change the level for those issues you want your customer to be able to view. Maybe you could even think about a listener that automatically changes the level based on a custom field (I'm not sure if I'd go for labels)

If you're using the JIRA suite utilities plugin you can add a "Hide transition" condition to the transition. The button will disappear for the user but it can still be triggered from another workflow function / plugin. Hope that helps

Have you turned off auto-watching globally or for that specific user?

Hey, if you're looking for issues that have been updated "yesterday" or the day before yesterday your JQL could look sth. like this: updated >= endOfDay(-3d) AND updated < endOfDay(-1d) Cheers Christian

We have established a connection to Confluence via Webdav and webfolders. That solved our problem as from now on we are able to adress the location of the different spreadsheats (via their URL (webfolder) or the specific letter of the mounted network drive) Here is how you do it:…

Hey, check this workaround: Workaround The config lives in an XML file: <tt><confluence install>/confluence/WEB-INF/lib/confluence-x.x.x.jar/preferences-default.xml</tt>. You need to change the boolean value to false, thus: <preference type="Boolean"> <name>confluence.prefs.watch.my.own.content</name> <value>false</value>…

A fact for a fact: https://confluence.atlassian.com/jira/created-vs-resolved-issues-report-185729594.html Have you tried to google your "statement", which is, as nic mentioned, not a question? Cheers

Look at the upper right corner. There should be a "cog" icon if you're an admin. Right between a question mark icon and your user avatar...

Maybe because you aren't a JIRA admin?

Why don't you just edit the default issue scheme according to your needs?

Hey, I wouldn't know. Sorry, Cheers Christian

We are talking about Confluence, right? Have you thought of the "share" function? That way the person having a questing could directly adress the SME. Other that that you could use mentions in your comments. "Question...@SME". I wouldn't use labels since you'd be messing up the labels with last names. Cheers Christian

You might want to describe what you "figured out" so people running into the same problem can benefit from your solution...

Could you post a screenshot of your workflow? To me it seems like you haven't configured any outgoing transitions form the "Requirements" step.

That hasn't anything to do with you being the admin. For example, the standard JIRA workflow often uses the "current assignee" condition which means that only the current assignee can transition the issue. So, if your workflow is defined to assign the issue to someone else (not YOU) you wouldn't see the workflow buttons…

I would look at the workflow "conditions" on all the outgoing transitions. Maybe you don't have the right to transition the issue. Cheers Christian

Could you please provide a version number since I'm trying to avoid this problem. I'm about to update both JIRA and JIRA agile... Cheers Christian

The fact that you can't edit closed issues most probably is being caused by a property on the workflow step "closed". Probably you'll find jira.issue.editable =false https://confluence.atlassian.com/display/JIRA/Workflow+properties Either you delete that property or, as I do it a lot, change it into…

But be aware that editing the core velocity files will have effect on all notifications that use those files (in this case using the issueclosed.vm). I would probably create an extra template and an extra event which would give me all the flexibility I'd need...