Jack Brickey Expert

You can import customers with the goal of creating the Customer users into you instance. However there is no means of capturing the customer’s profile info like phone number. With that said, if you have CSV emails then you can simply copy and paste into the Add customers box within a project.

When you speak of “sign off process” does that equate to workflow? If your teams need/want different workflows then certainly consider us8ng different issuetypes. It is difficult for me to covey what I might consider to be the best solution without really understanding your process details. I might consider a single…

I checked w/ some Atlassian colleagues and they confirmed my suspicion that you had a trial that has expired. Atlassian Support will ultimately get back with you on this.

yes. use Automation. Trigger - issue transitioned from (any) to Ready for QA Condition - if/else block and inspect for each component action - in each if/else leg use Edit issue and set Assignee

keep in mind that "time in status" may not give you what you really want. if you are interested in seeing how much time went into testing an issue that might be a fraction of the actual time in status. The issue could sit in the QA status for hours or days before someone gets to it. So you might want to consider a two step…

i suspect there is something not right w/ your account or billing. Did you open the ticket as a high priority?

Hi @aravind , is this Jira or Jira Service Management? To be clear here, it seems that you are saying the footer is being applied to Customer responses not associated with comments that your Jira users/agents are making, correct? Is it possible that you are using an email app addon like JETI or JEMH? Please check under the…

sure. just create a unique workflow w/ desired statuses and associate the sub-task issue to that workflow. you might find this read useful - Workflows 

there are a few, just not associated w/ color schemes. if you happen to use a Mac consider the desktop app which support dark mode.

you technically can't make a sprint inactive. What you can do is to stop the sprint which will push all of the incomplete issues to the next sprint. If you have any issues in the 'done' right most column move them out to the left so they don't get marked complete.

Hi Lorie, welcome to the Community. So I assume you are using a Classic project. What are your swimlanes based upon (epics, queries, etc)? Check under board settings > swimlanes. Maybe the board owner changed the swimlanes config. Please provide more info and if appropriate, screenshots.

I don't see anything in your requirements that would drive me to a different workflow. I would definitely not create different issuetypes. The "which product" can be covered either by different projects, which I sounds like you already have (?) or maybe Components w/in a single project or custom field.

Hi Victor, welcome to the Community. As you pointed out changing the background is a system setting so it indeed changes for everyone. I am not aware of any open suggestion for this but you can have a look at jira.atlassian.com. TBH in all my time in the community I have not seen this requested. Doesn't mean it wouldn't be…

well first off... Do not do that! Deleting issues is almost always a bad idea. Giving everyone a gun is most certainly a bad idea. off of my soap box... looking at your images you are on the right track in that you would use "any logged in user" for each project - project settings > permissions > delete issues. I'm not…

Well, in fact I could if I was a developer for Atlassian and I thought it was the right thing to do. But I am simply a customer like yourself. ;-) I did find this old issue you might want to vote. However, you will note that only 5 people have voted for it and there are issues outstanding with many many more votes. Not…

yep. you need to rethink why you are excluding statuses in your filter. this is not a normal thing to do. if for any reason you don't want a status to appear on the board just don't map the status to any column.

well I checked status.atlassian.com and don't seen any reported issues for JSM. If you are still seeing this be sure to check multiple browsers (don't suspect this is the issue though) and then reach out to Atlassian Support. 

There is a good response from An Atlassian Team member here - Does-JIRA-Cloud-slow-down-if-there-are-a-large-number-of-issues . One thing to check is the number of issue without Resolution.

Look to Automation. For example... trigger - issue transitioned conditions - optional based on you needs action - add comment and share with customer OR send email to Reporter. I prefer the first as the comment provides history

I believe the issue here is that your rule runs every 24h but simply acts on any issue that is in the WFC status regardless of how long it has been in that status. What I do to manage this IC is to define an SLA that starts when an issue enters the WFC status and ends when it moves out of the status. Then the rule can…

You will want to do the following (assuming Classic project): * workflow transition to Test status needs a Condition that requires Assignee not empty * workflow transition to Dev status include a copy field Post Function to copy from a “DEV assignee” custom field into Assignee field. Note the need to create this custom…

please contact Atlassian Support. If you are having this on all projects for all users something is amiss.

sorry my bad... i see you are on Server so there is no "new issue view".

one option would be to consider adding a label to the epics where you are assigned an issue. kludgy. 

for sure. however, i was assuming you wanted something where the email happened once at the time it was set. with reports it would send an email daily (?) and include all issues that meet the JQL filter.

reach out to Atlassian Support and select billing option

So I think the issue is that the "Flagged" field that is being referenced in the Automation is not the same as the "Flag" for NG projects. I suspect that you can't get there from here on NG at this point. However, it may be possible via the "more options" but I am just not sure. Maybe a quick support ticket w/ Atlassian…

yes. that is the correct process for sure.

well I just found it referenced in the docs - add-your-team-to-next-gen-boards . So let me have a look at something and test it out.

disclaimer: I don't use NG projects but I'm unaware of Flagged applying to them. Do you have a different experience? can you point me to where this feature applies to NG?