Susan Hauth [Jira Queen] Community Champion

tempo?

Security levels only define whether an issue is visible or not. There isn't any granularity to view versus edit for security levels, that's only by permissions. 

You should be able to do this still using a single notification scheme. Maybe you need a new event for just this situation?

Hi Vic, Really need this feature as well. Vote for: https://jira.atlassian.com/browse/JSDSERVER-1034

It is currently not possible. Vote for https://jira.atlassian.com/browse/JSDSERVER-1034

Vote for https://jira.atlassian.com/browse/JSDSERVER-1034

Vote for https://jira.atlassian.com/browse/JSDSERVER-1034

Awesome tips. Of course I'm going to be following you around in Barcelona, so good to know you're prepared, even if I"m not. See you in 2 weeks!!

I havent' seen any ability to provide edit ability on JSD for the customer. Maybe you could try the automation rules and pick up on a phrase "Priority high" that would then modify the Priority? 

This feature seems to be only available if users are grouped into Organizations and then you can see all the issues within an organization as long as the issue has been shared with the organization.

We experienced the same problem and it was related to a bug where a user that had been renamed could not perform the action. Fairly obscure. It's actually a bug in the plugin JIRA Toolkit. Not resolved yet. https://ecosystem.atlassian.net/browse/JTOOL-238

From what I understand you need to enable the Notification "Organization Added". This will then include the customers in the Organziation as part of "Customers Involved". It's not really that well explained in the description.

Thank you that worked!!

Hi, I added that in and then tried preview and this is what I got: GlobalThe indexer for this field expects a java.lang.String but the script returned a com.atlassian.jira.issue.customfields.option.LazyLoadedOption - this will cause problems.So it did read the custom field Department (which is a single select field).

Many thanks, that worked perfectly

I can recommend the plugin from Valiantsys: https://studio.plugins.atlassian.com/wiki/display/VSLA/VertygoSLA which can manage the whole idea of a clock and has the ability to "freeze" statuses. Take a look

Hey guys, please vote for this issue: https://jira.atlassian.com/browse/JRA-60483

Thanks!! Sort of. Would be really nice if it had an Issue View. But at least I know it's not my configuration. I do appreciate the help.

I think it's JIRA toolkit, but I'm not 100% sure. I have tried googling and cannot find it. I have attached the custom field type as it shows when creating the field.

I'm not seeing it anywhere on the View Issue Screen but would have expected to see it in the User section. The field has been added to the Screen configuration. We are on JIRA 4.4.3.

Hi, I do this quite often. If you have miscellaneous workflow extensions which you should if you don't already https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions Then you can in a post function copy the Supervisor to the Assignee field. Susan

I think it had to do with not being the project administrator. It seems it lets me into the edit Project details and I can upload a new avatar, BUT if I'm not the actual administrator for that project, it won't save. But it let me think I had added the avatar.

In my test account, I don’t know how to see more Customers, leads, etc According to the Tempo User manual, we should be able to see “all accounts”

Me too!! I"m having the same problem in JIRA 4.4.3 trying to import. In JIRA 4.1.1 I had the .csv importer working perfectly, and now I don't get step 6, and the importer didn't recognize any of my custom field names and created new ones and then it told me it imported 108 issues which are nowhere to be found!! Not…

@Dataloy VMS, we have the same requirement. Were you able to configure the SLA to make this work?

Ah...yes, one of the field names was not a duplicate of another type of field, so I have modified and it works like a charm! Thanks very, very much Jamie.

Hi, Well it didn't blow up so that's a positive step forward. But it calculated 0 where it should have calculated 2.25 for the test issue. effort = 3, complexity =3 , urgency =2, need =2 ;-)

Resolution was to put the set Security Level from user priority as Step 1 in the post workflow BEFORE the Issue is created initially. This was definitely some sort of change from JIRA 5.0 to 6.1 because it used to be after "Creates the Issue initially". Thanks David for your patience and testing!

It would be awesome if it worked, but it doesn't in JIRA 4.4.3: https://jira.atlassian.com/browse/JRA-26284 Grrrr. Atlassian, please don't change these things without testing!!

Problem Solved! the Project Role was "Operations " (2 blanks on the end). Argh. I edited the role name and voila all is fine again. Guess 6.1 wasn't as fussy! MANY THANKS!!!