- Alertly was made for and can be used by teams that are working with Slack and JIRA for making tem communication more effective as well as to run various project management purposes.
- If you’re a Slack user and you wish to integrate Alertly with your Slack account, all you have to do is just click on the “Add To Slack” button in the alertly.io site.
- Once you do this, our bot @alertly will be added to your Slack team and will be ready for use. Also, your user authentication and credentials are verified by Slack OAuth itself.
- Actually, no. even after adding Alertly, you still will be not able to receive the alerts until and unless you connect your JIRA project.
- We are managing all alerts based on JIRA projects and this means that JIRA connection is required in order to start getting alerts.
- We are supporting both on-premises as well as cloud based JIRA software. However, in case you operate an on-premises JIRA software, you have to make sure that the Alertly IP address 139.59.52.174 is allowed to run and operate on your firewall.
- For you to connect your JIRA account, you have to first create an application link in that JIRA account. It is worth noting that this link can only be created by the JIRA administrator.
- All you have to do is follow all the steps shown in the site during JIRA connect and you’ll be good to go.
- After successfully creating the application link, the admin will also have to authorize the Alertly app by clicking on the “Authenticate & save” button as a last step on the Alertly site.
- In case you are still facing any additional issues in the JIRA project, please feel free to contact us at hello@alertly.io.
- No. For you to effectively authenticate Alertly in JIRA, you must be an admin of a JIRA account.
- Only admins of JIRA accounts have the ability to create Application Links to authenticate Alertly with JIRA.
- The first step is for you to carefully double check the information you entered during the application link steps.
- If your JIRA software is self-hosted, then make sure that you give the Alertly IP address 139.59.52.174 allowance on your firewall.
- Still getting same error, contact us at hello@alertly.io
- After successfully authorizing your JIRA account, you can add projects from the very next project selection screen.
- You can also add more projects from the same JIRA account if you’re on the admin panel.
- This is most probably due to the fact that you don’t have access for it. It is also possible that your access has been revoked.
- If the project is already added by someone from your team but that person did not grant you access for that project, then the “Request access” dialog is most probably going to pop up if you try to add the same project.
- You will be shown the name of the user who has already added this project before you and you can send a request from that screen to that user along with reason why you need to gain access to that project.
- When the user provides you access, you will be able to see that project in your dashboard along with the alerts setup for that project.
- You can only the delete the added project if you are an admin or an owner of the Slack team.
- The project will be visible to all team members, but the users who have access to that project will only be able to view and modify the settings and alerts of that project.
- You should also know that any user who has no access to that project will not be able to see the dashboard.
- Yes. It is possible or you to add up to 5 JIRA accounts from here: Username ⇨ Admin Panel ⇨ Accounts tab ⇨ Add another JIRA account
- Currently, you can only add up to 5 projects in each JIRA account and we have limit of 5 JIRA accounts. This basically means that you have the freedom to add up to 25 projects.
- Once you select the project, you can manage the groups/teams by assigning various tags to your teammates. Also, you can select the reporting head of each user if he/she is reporting to someone.
- You can see this screen very next after project selection screen.
- You can also manage groups/teams later on from admin panel by visiting Admin Panel ⇨ Project ⇨ User Management Tab.
- Add tags
- Alertly automatically maps JIRA users with their corresponding Slack users on the basis of their email-addresses.
- You can see this screen very next after user management screen.
- Also the user can configure these mapping later on by visiting Admin Panel ⇨ Project ⇨ JIRA Slack Mapping.
- Alertly provides feature to view the events and other details of a project to certain users, these access can be decided by the user who configured the project.
- One can easily grant and revoke access to user whenever required.
- You can see this project access screen very next after Slack-JIRA user mapping screen.
- You can also grant/revoke access later on by visiting Admin Panel ⇨ Project ⇨ People.
- We are supporting 3 types of events: 1) Follow-up event, 2) Custom event and 3) Field-watcher event. Once you successfully create any types of events, you will be able to receive the alerts.
- You can also add the events from our “Events store”, if you don’t know how to create these events.
- You can also try out created alerts by just clicking on “Try Now” button after adding all the required details.
- Follow-up events are used to receive static alerts at defined time. They just worked like reminders.
- You can also trigger these events on sprint start/end or on version released, so you will be able to pass required alerts at right time.
- Everyone can receive this alert if they are in the receivers list.
- Now if you want some alerts based on JIRA data then this is event which helps you on that.
- You can also trigger these events on sprint start/end or on version released, so you will be able to pass required alerts at right time.
- Everyone can receive this alert if they are in the receivers list.
- These events also provide summarised report of the team as well as an individual summary to users.
- Yes you can post these alerts in particular channels and also in private groups.
- If you want to receive only your issues/tasks, then select your name with appropriate JIRA field like “Assignee = John” or “Reporter = John” and keep your name receiver list.
- If you are thinking to post same alert in channel or private group then make sure you invite @alertly bot in that channel/private group.
- There is no formula needed, just keep “Assignee” field in receiver list and they will receive only their issues/tasks.
- Yes, you can use aggregate functions to get summarised report of the issues obtained from the formula. You can add aggregate functions in the message by pressing equal to (=) symbol and add functions from the list.
- Yes, Alertly supports emojis also in the template. You can add emojis by pressing the colon (:) symbol in the template text and select an emoji from the list.
- Yes, you can create event that depend on related issues/tasks such as when you want to find issues that have Bugs or Sub-tasks defined under them.
- You can add these filters in the Advanced filters section under the main event formula in the event builder. It is available only with Custom events.
- Yes, we support Service DESK project. You can add this project like any normal Software project and setup alerts for yourself.
- We currently support JIRA Software and JIRA Service DESK.
- Yes, you can add alerts based on Sprint by just adding Sprint to your filters.
- If you would like to watch on some JIRA fields then this is the event for you.
- These kind of events trigger immediately when a certain action is performed on JIRA issue field and that field is watched for a change.
- You can also limit your alerts by providing extra filters with the field to be watched.
- Yes, you can change the attachment color for every field-watcher event you create.
- You can change the color from the color picker and also see how it will look like by seeing the affect in the template on the left.
- This provides a grid of cards for currently set up events for the selected projects. For every project added and users configured, Alertly automatically sets up various events for the user to provide them with easy onboarding.
- The user can change those events as well as add new events as per requirements.
- Also, the user can filter events according to types from the filter given on the top right corner.
- The user can stop the event from triggering at any time by just pressing the switch available on the card at lower right corner.
- Alertly provides various easy to add events to users, so that they do not need to create any events from scratch.
- The ready to use events mainly contain filters and template text along with the description.
- These events can be easily added to your dashboard and then modified according to requirements.
- You can visit the Events Store by clicking on Dashboard ⇨ Events Store.
- Alertly provides feature to add custom template for every alert created.
- User can add emojis, jira fields as well as aggregate functions within the template along with normal text.
- Alertly provides extra features to make alerts interactive (custom events only).
- The user receiving alerts can update the issue fields like status, due date from the Slack itself.
- Actionable alerts will help users to take actions on JIRA issues from their Slack itself.
- Daily:
- Alerts trigger everyday at the specified time.
- Alerts trigger everyday at the specified time.
- Weekly:
- Alerts trigger weekly on the day specified at the specified time.
- Alerts trigger weekly on the day specified at the specified time.
- Monthly:
- Alerts trigger every month on the date mentioned by the user while creating event at the mentioned time.
- Alerts trigger every month on the date mentioned by the user while creating event at the mentioned time.
- Version Released:
- Alerts defined with this frequency are triggered immediately when a version is released from the JIRA.
- Sprint:
- Events can be scheduled to trigger when sprint starts or sprint ends. This frequency provides with options to trigger events at certain days from Sprint dates as defined by user.
- Events can be scheduled to trigger when sprint starts or sprint ends. This frequency provides with options to trigger events at certain days from Sprint dates as defined by user.
- Events can be triggered at the user defined timezone also.
- User can set the timezone according to which they wish to receive alerts for that event.
- Event alerts can be sent to direct users, or channels or private-groups or individually by JIRA users.
- Sending alerts to any JIRA user field will send alert containing only those JIRA issues which the user is related to.
- If you create your event as Public then anybody who has access to those project can modify that event.
- You can change the privacy of event by pressing the switch at the bottom right corner on the event builder screen.
- Yes, events can be marked as private, if the owner of the event does not want any other user of the team to modify current event. Event can still be viewed by other users.
- You can copy any existing event by opening the event and pressing the “Clone” button at the lower right corner beside the Archive Button.
- The event will be cloned and open as a new event which you can modify according to your requirements.
- Custom events and field-watcher events provide options to add various filters for events to trigger.
- These filters can also contain round brackets ( ) to make complex formula.
- Extra/advanced filters are used to narrow down the result. It works on dependent issues/tasks in custom event.
- You can reconfigure JIRA projects again by visiting Username ⇨ Admin Panel ⇨ Select related project.
- You can then change any of the settings for that project.
- Accounts:
- This screen provides user features to add new project within a JIRA account or add another JIRA account.
- It also displays the list of accounts and projects configured within the Slack account.
- User can disable project to disable all its events or delete projects and accounts.
- The removed projects can be added again by adding new project within the account.
- It provides option to re-authenticate the account if the token is expired or invalid. User can also update the JIRA fields or users if added after configuring the application link.
- Tags:
- It also provides options to define new tags as well as modify the existing tags.
- It also provides options to define new tags as well as modify the existing tags.
- Slack:
- The logged in user can sync the Slack users directory if new users are added to the team.
- The logged in user can sync the Slack users directory if new users are added to the team.
- You can visit this by clicking on the Username ⇨ Admin Panel on the top right corner.
- Whenever user clicks on certain project within a JIRA account in the admin panel screen, they can edit or view the currently configured settings for the project.
- You can visit this by Username ⇨ Admin Panel ⇨ Click on any project you wish to view.
- User Management:
- User can modify the tags and reporting heads for each user.
- User can modify the tags and reporting heads for each user.
- Jira-Slack Mapping:
- User can also modify the corresponding JIRA user if required.
- User can also modify the corresponding JIRA user if required.
- People:
- Users can grant or revoke access from certain users so as to hide the events and project settings from that user.
- Users can grant or revoke access from certain users so as to hide the events and project settings from that user.
