Jack Brickey Expert

I would create a new issue in the SW project. Use the “create linked issue” feature in JSM. 

I don’t know how Zendesk processes emails. JSM will processes unread emails. So if Zendesk processes an email and it is marked as read before JSM gets to it then a ticket won’t be created in JSM. Typically I cut over from my be product to JSM on a weekend and simply switch the email over. I basically shut down the old…

Hi Cameron, I spent a good bit of time in the community and one of the common asks are centered around migrating from other products onto the Jira platform. It seems to me that Atlassian is missing an opportunity by not actively providing migration tools from various platforms. In fact I do recall seeing this as part of…

Yes that is “fancy-talk” for what I said. 😂

I believe I see the culprit here. You will note that there are two issue keys in the subject. I suspect that JSM is not able to discern which issue should be commented.

Here is one common use case for this… Agent moves issue to Resolved and you require/allow the Customer to designate their issue as Closed. The proverbial fox in the hen house.

So if your workflow is well formed (see end of post), where the Resolution is concerned, then you don’t need, or want really, to have a PF to clear the Resolution on transitions from any status except where the resolution has been set. In other words, if it isn’t set you don’t need to clear it. Now if you have issues in a…

OOTB there isn't a good solution for time in status. You might consider an addon for this. arguably you could create custom fields for entering and exiting statuses coupled with automation but that is less than ideal.

you can reach out to support to request increase. however before doing so I encourage you to see if you can optimize your SLAs. I ran into this previously and realized that I was not setting up my SLAs effectively.

The strikethrough as you mentioned is associated with the resolution field. Simply put once an issue is resolved, which equates to any value in the resolution field, then the issue has a strike through. If you ever re-open an issue you must ensure that you clear the resolution field. You do this in CMP projects via a post…

That would be nice for sure but unfortunately not. I suspect that there is an open suggestion for this. You may wish to search jira.atlassian.com for such a suggestion and vote for it.

Description should be exportable. I just was successful. How exactly are you doing your export?

@Kishan Sharma , while what you suggest is possible I really do not see this as an issue. There are a number of holes with the kudos program but the team is doing a great job at resolving them. Keep in mind that while we, as Members or even CLs, cannot see the details of where someone’s points come from the Atlassian…

duplicate post - When-a-user-replies-to-a-JIRA-notification-email-a-new-ticket-is... 

there may be a limit on the number of fields. try removing some.

ensure that the user is replying to an email notification that includes the issuekey in the subject. they should not respond to original email that was sent to create the issue,

there isn't a way to do this in cloud OOTB. you might check the Marketplace for options.

it may be that you are using TMP? If so that could explain it as I suspect that parameter is CMP only. 

project = TISSDEV AND component = SOS AND status in ("On Hold: Missing Information", status = "On Hold: Technical Issue Preventing Development")

what do you mean by "incorrect entry". Do you want to allow them to delete issue? Assuming so let me first offer that giving delete issues permission is generally a bad idea. That said Delete permissions can be given via project settings > permissions > Delete Issues

if you are referring to how sub-tasks are displayed within the parent you can modify the system parameter under admin > system > advanced settings >> jira.table.cols.subtasks. please observe that this is a global parameter.

Yes "it" is a reserved text search string. Please refer to this document - search-syntax-for-text-fields here is the pertinent excerpt... Reserved words To keep the search index size and search performance optimal in Jira, the following English reserved words (also known as 'stop words') are ignored from the search index…

Hi Linda, welcome to the community. You can use the CSV importer to import issues. If one of the columns is components and you have listed all of the various components in at least one row then the importer will create those components upon import. So you will have to create some dummy issue that you subsequently delete…

Are you setting the “Epic Status” to done not just the issue “Status”?

Ok, so now I am suspecting that maybe this is an add-on to integrate fresh desk with your JSM project. Is that possible?

Hi Sean, i’m a bit puzzled because you mention adding an initiative which I did not think was supported in free. It is not there in standard and I believe it is only in premium. in free and standard you should have epic > story/task > subtask. Further, the relationship between epic and story/task leverage is the epic link.

Hasta donde yo sé, esto no es posible. Aquí hay una sugerencia abierta para esto - JRACLOUD-75991 - Possibility to copy attachments through Automation rule 

not via the UI. You might check the APIs if that is an option.

Hi Alan, I am not sure I am following. I tested on my instance based on our post but not seeing an issue. Maybe you could illustrate with screenshots or video clip.

Epic Link does not apply to TMP. Epic Link is replaced by "parent" if you are using in JQL.