Jack Brickey Expert

+1 for converting to numeric field

You would need to use an addon app for this. In Cloud we have Automation for Jira built in and I like the capabilities. If you have Scriptrunner, Power Scripts or similar you could use that. However, let me ask if that is the right approach. Is your ultimate goal to not have folks use email to open issues? If so then you…

I would use Automation. Basically... trigger - issue transitioned condition - status = done condition - any other condition to ensure you zero in on only the issues you wish to reassign action - set assign to new user there is more to the details but it is difficult to be specific without the details. 

Post Function won’t get you there. Look to create an Automation rule... trigger - issue created condition - field value action - create issue

Are you sure you are logged into your instance? Is your avatar show in upper right?

The only way for users to see issues that they did not create is to be a Request Participant of the issues. To do this you can use Organizations to group your users and the share all issues with the organization. Note this will result in all users in that org receiving notifications on changes to each issue in accordance…

Hi Richard. I’m not following. If you have created a cloud instance you should have a URL to that instance, e.g. abc123.atlassian.net. Are you trying to add products to your instance or what?

у всех вопросов есть ключи. они состоят из ключа проекта и порядкового номера, например ABC-123. Я надеюсь, вы это понимаете, поэтому мне непонятно, понимаю ли я его вопрос.

So you are saying that the RT is not empty and yet you cannot configure the layout? Screenshot please. Are you an admin?

If you want the client’s issue to be uniquely identified yes. If you don’t care who the reporter is then you could not check the create user box and simply choose a default reporter, e.g as yourself. 

Sure. You could create a dashboard which might be the best solution for the execs if they have access to Jira. Otherwise just create a JQL filter and use it to export to excel/sheets. 

It depends on your requirements. If all you want to do is to create TCs and treat them just like other Jira issues then just create new issuetype. However if you wish to have a more elaborate solution look to the many test addon apps in the Marketplace. 

Yes this is by design. It maintains the history of where you planned to complete the issue but did not. It ensure historic sprint reports are accurate. 

Yes. Every user in Jira needs to be licensed so if you create the user that user will be counted into your total licenses. 

I recommend you review this article. create-issues-and-comments-from-email you will need to create an incoming email handler unless you are using JSM which is a bit easier. 

Sure. Have you attempted and having issues?

Are these Opsgenie incidents or JSM issues? If the latter please verify that the Resolution is cleared (empty). 

All of your SLAs need to have a Stop on ‘close’ element. Is this not the case? Feel free to share an image of your SLAs

Hi Anne, to be clear are you saying you had a Free test instance stood up and no longer need and simply wonder if you need to take any action? If so, no you do not. It will eventually be decommissioned based on inactivity. You likely will receive an email notifying you of this several weeks from now. With that said you…

Hi Soumyadeep, I wouldn’t think the software would trigger based on time in Community. I base this on my own online efforts as well as others. I would believe that some pattern matching might have triggered the algorithm. I do recall several duplicative content articles that you posted over the past couple of weeks that…

The reason you are seeing this error is that you have Epic Link field in thee create screen you are using when creating an epic. Basically you are using a single create screen for all issue types. Then if you select Epic as the issuetype during the create the error will appear. It want cause any issue unless you attempt to…

Yes you can do this. Here is how I would approach it. trigger - issue created condition - JQL — request-channel-type = email action - edit field

good to know. A couple of things to leave you with. Are you the only admin? If not you might want to chat w/ the other(s). * have a look at the audit log (limited in cloud) and see if you see anything that might have changed to explain why it is now back. admin > system > audit log * here is a link to Atlassian Status…

what you need to ensure is that an Agent in any given project is not also a Customer in the same project. How you ensure that depends on you situation. But, if this is happening because of a cross-project organization then you need to extract the agent from that org OR decouple the org from the project.

Hi Sheri, are you using Classic? Kanban or Scrum? Were the issue there previously or is this a new board? One possibility is that you don't have any statuses mapped to backlog. Go to Board settings (Classic only) and Columns and see if any status is mapped to Backlog.

well I was just thinking that you might have a rule that triggers when an issue is create or edited and search the field for an email and if it finds one then a label is added. then you can simply use the label in a JQL going forward to check for issues containing and email. Now, whether this makes sense or is doable…

is it possible to get a screen shot of this? do other customers experience this? have they tried another browser? can you log in as a customer and reproduce?

Hi Ineke, I need to back up here a bit. So are you talking about moving issues w/in the Backlog screen where you can drag/drop to "Rank" them or are you talking about moving an issue w/in the board from column to column? The reason I'm asking is that your OP seems to convey w/in backlog (ranking) but your images are of the…

that is precisely what you must watch out for. in this case you need to separate the organization into two orgs (per project) so that you don't run into contamination.

this cannot be done OOTB. You can either consider different dashboards per team or look to the Marketplace for options.