Jack Brickey Expert

This strikes me as problematic and surely inaccurate. Regardless I don’t know of any way to accomplish. Why not simply allow the customer to reopen an issue from the portal?

Related question

Robert, i think the issue is in your filter. ultimately the way it is written I suspect is not what you intend and to be honest I'm not 100% sure what you are intending. But let me throw something out there to see if we can get this resolved. Let me propose the following alternative: project = SIP AND (summary ~ "Mission"…

but walk-ups and phone are methods of entering tickets into the system. With that said I see where you may wish to capture that data. I assume the agent would be the one to open on the behalf of the reporter. So.... You could consider adding a custom field to meet your needs. If the agent opens they would be required to…

there are only three possibilities: email, portal, application (Jira). they are not editable AFAIK. What other channels were you thinking of?

agree w/ Nic here. Core really is best suited for 'business' projects not development or handling customer requests.

ha....yes...what Alexey said. :-)

Server or cloud? Basically you are simply dealing w/ permissions/security. You can define a group that is 'read only' and place those users into that group and then give that group Browse permissions. read more here: https://confluence.atlassian.com/jirasoftwarecloud/permissions-overview-764478244.html or find the version…

you need to add the Due Date to the create screen associated w/ the project. Go to project > screens.

@[deleted], finally completed. here are some pics.

There are two approaches: * Add a Post Function to your WF(s) to set the resolution to Done* edit each WF associated w/ the project (use diagram mode) * double-click each transition into Closed * open the Post Functions screen * Add a post function to set the issue field and select Resolution and Done. * publish the WF *…

go into the View issue detail view. click on the CS-64

check the Resolution field of CS-64 I expect it is unresolved.

I would suggest using automation. There are a number of addons that could help, e.g. Automation for Jira Lite. 

The import is intended as a migration tool where you plan to move away from bugzilla. It sounds like you plan to continue to use bugzilla along with introducing Jira? Unsure why that would be the case. However, my confusion aside, you can certainly import issues into an existing project using a ‘daily CSV file’.

I never really placed an estimate on an Epic. Can you not simply set the estimate to 0?

@[deleted], as Nic indicated, if you want the T2/T3 to be assigned the customer issues and track the, via SLA then you should use JSD and set them up as agents. 

Ah, now I see. This is for the customer to manipulate not the agents. Sorry I missed that. I don’t know of any manner of controlling what the customer sees on the portal by the Organization they are in OOTB. I would recommend search the marketplace to see if anything exists. 

Have a look at these threads: * https://community.atlassian.com/t5/Jira-Software-questions/Dashboard-Gadget-Actual-VS-estimate-time/qaq-p/588176 * https://community.atlassian.com/t5/Jira-questions/Estimated-vs-actual-Actual-Time-Spent-Report/qaq-p/27046

you can name the versions whatever you want for sure. I find this messy but if it works for you go for it. The process I was proposing is IMO cleaner BUT you loose the capabilities of releases built into Jira.

I would again point you to automation. I set this up on my test project using the aforementioned (free) addon very quickly (5m). It looks something like this: * When: issue created * If: matches* project = test and creator in (E1, E2, E3) * Then: Assign the issue to M1 * Else-if: matches* project = test and creator in (E4,…

if you are following the instructions and it isn't working I would certainly open a ticket. I'm on cloud and it works fine so maybe something is up w/ your version of server.

vote for this suggestion - JSDCLOUD-1733

From what I recall it is supposed to work that way. But I just tested in cloud and it did not work for me. I even searched for past discussions and found this - https://community.atlassian.com/t5/Questions/Configure-issue-priority-based-on-email-priority/qaq-p/76255

this is a bit tricky and a bit of a hack so I don't generally recommend it but... Acquire the SprintID (not the name): * using Firefox * display the View issue screen * click on the Sprint field as if you are going to edit * hover over the current sprint link * bottom-left will display the 'url' w/ the SprintID=xx.…

Edit the story directly in the View issue screen. Search for it and edit. If the sprint field there are some tricks to do so but won’t go there unless we have to. 

You can also consider automation using something like Automation for Jira Lite or similar. 

If you mark the issue as done and set the sprint to the closed sprint does it achieve your goal. 

Hmm, based on your question I gather that the current solution doesn’t allow time logging. I assumed it would. I haven’t tested this yet but may give it a try later. 

I recall looking for this a couple of years back but found there really aren't any configurable release rules. Maybe that has changed but I haven't seen any sign of that in Cloud at least. Here is a good read you might be interested in but doesn't help w/ your requirement. You may check the marketplace.