Jack Brickey Expert

Is the "user" in the CC of the 'create-email', i.e. the message from EA1 to EA2? how are customer permissions configured for sharing? See image. if you aren't using Organizations try what I illustrate. here is a snippet from Atlassian documentation: Add participants via email If you create or respond to a request via…

not natively. you can use an addon like Scriptrunner or maybe EazyBI or others.

You can accomplish OOTB as follows: * create separate workflows for each issuetype that needs special treatment * add a post function to set the custom field value

Certainly a reasonable approach. I really haven’t used flagging much. The last time I looked I recall liking it but just haven’t fit it into my processes formally. The one caveat I would make here is if you have one issue blocking another I would certainly use the blocks link method. Note if you wanted to use a Kansan or…

I’m wondering if Jira Service Desk would not be a better option as it allows customers to create issues via email and portal. If your requirement is to have everyone use the application directly, however, then they will require paid licenses.

Thanks for the detailed description. As the referenced thread indicates, the only way to get “user” to be reporter would be for the agent to update the issue. However if the “user” is on the CC they should be added as a participant as the other thread conveys. What you lose in this scenario: * visability of who reports…

I need more info to be able to offer effective ideas I expect. What do you mean by track opex/capex? Do you want to simply filter on issues that involve these or do you want to total expenditures. For the former you could do this via uniques issuetypes or a custom field or maybe components would work. I don’t see Jira as a…

It think it does explain it. I expected the unresolved to be the culprit. Was the suspect user in the User5 position in your filter? I suspect so. Consider the following alone... assignee = user5 AND resolution = unresolved as soon as an issue becomes resolved it will disappear. The “AND resolution = unresolved” was only…

@Rick Baker's followup inquiry brought me back to this topic and I wanted to respond to @Henrik Sihvonen's last comment. The solution of only receiving reminders for 'your' issues, whoever 'you' are is a simple matter. there are two methods: * good: each user that wants a reminder simply creates a filter w/ their name as…

assignee IS Empty

to share a dashboard a few things need to happen: * the individual must be a user defined in your Jira instance. that is, you can share w/ someone that does not have access to the application. * the filter used on any gadget must be shared w/ those you want to have access. I typically share w/ any logged in user. This is…

@John Crafton, it seems you simply want to allow customers to access the portal to create issues and search a knowledge base. The portal is there as soon as you set up a project (before actually) and the following article should explain how to set up your KB.…

Glad you found it. I concur that the Portal would benefit from a bit of an overhaul It wouldn't take much and I expect Atlassian will be doing just that in time. Especially on Cloud as we get to trial most things before they find their way to Server. ;-)

service desk customer can only view tickets from the portal not w/in the application of course. they do this via their profile icon on the upper-right corner of the portal. They can only see the issue they created or those that have been shared w/ them.

Welcome to the Community. Based upon what i read here this is easily done via a number of methods. Providing Reports to Managers - this can be done via a dashboard for each manager or by setting up filters w/ regular subscription delivery. You can create a custom field called "Department" or whatever and ensure that the…

BTW...here is details for accessing User Management: * click on the top-most left icon (Jira) * click on Settings * click on User Management

this is a duplicate

if you are truly a Jira Admin then: * Go to Settings > User Management > Groups * Create a group and add members * Go to the the project in question - project > Settings > Permissions * Assign the group you created in #2 to the permissions you wish them to have more info here…

I concur w/ Danyal here. It is much better to enforce time logging and track progress in that way. Comments are simply too subjective and unpredictable since some user will ramble, some will be vague and some simply want comment. Of course, one could make a similar argument about time logging but IMO it is more easily…

If you are not a Jira Admin you cannot. Have your Jira Admin create the group for you. Then if you are a Project Admin you can apply the group to the project in question on the Permissions view.

Not exactly sure w/o fully understanding your environment and process but here is something that comes to mind. the issue here is that Components field can have more than one entry. So your could enforce a process where the user needs to replace the current component w/ a new one. This likely won't work all of the time…

I don't have experience w/ this but you might read this API

Danny, interesting for sure. i would not have guessed (obviously :-)) that! Unassigned is the same as empty so that wouldn't be the way I implemented. 

Server or cloud? Server there should be a gear/sprocket in the upper right (unless it has changed) Cloud click the upper left-most icon and then Settings

* I would suggest two methods here:* add a status to the workflow, e.g. "Hold" or "Waiting 3rd-party". in this scenario whoever is accountable w/in the team to 'manage' the vendor should be assigned the issue. * create a sub-task to the issue for getting closure w/ vendor and assign the proper person. * I would treat this…

There really isn’t enough info here to offer assistance. Can you explain what you mean by tracking dependencies. 

No. If one component is unassigned there should be no collision. Easy to test and verify. Sorry, I can’t help on the bonus question. Do you have some specific requirement. Might not need an addon. 

I don’t know of anyway to do this but maybe there is. However, just because someone is logged in doesn’t mean they are active. I never log out. 

IMO... First review comments should be an attachment or in the comments for the issue being reviewed. If the review comment is to result in changes that will be done within the current sprint I would log that work under the current issue. If the work will fall outside of the sprint I would open a new task, not sub-task,…

Do you get an email for each bug from supplier? If so why not use an email handler to create the issue in Jira?